summaryrefslogtreecommitdiffstats
path: root/dom/base
Commit message (Collapse)AuthorAgeLines
* Merge pull request #1262 from athenian200/solaris-workMoonchild2019-11-02-1/+5
|\ | | | | Support Modern Solaris
| * MoonchildProductions#1251 - Part 27: Fix ifdef style.athenian2002019-10-21-2/+2
| | | | | | | | This should do it for all the commits to files I changed, but while I'm in here I could probably go ahead and turn ALL the singular if defined statements into ifdef statements by using grep/find on the tree. On the other hand, perhaps we should do that as a separate issue so that this doesn't become a case of scope creep.
| * MoonchildProductions#1251 - Part 1: Restore initial Solaris support, fixed up.athenian2002019-10-21-0/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Compared with what Pale Moon had for Solaris originally, this is mostly the same zero point I started patching from, but I've made the following changes here after reviewing all this initial code I never looked at closely before. 1. In package-manifest.in for both Basilisk and Pale Moon, I've made the SPARC code for libfreebl not interefere with the x86 code, use the proper build flags, and also updated it to allow a SPARC64 build which is more likely to be used than the 32-bit SPARC code we had there. 2. See Mozilla bug #832272 and the old rules.mk patch from around Firefox 30 in oracle/solaris-userland. I believe they screwed up NSINSTALL on Solaris when they were trying to streamline the NSS buildsystem, because they started having unexplained issues with it around that time after Firefox 22 that they never properly resolved until Mozilla began building NSS with gyp files. I'm actually not even sure how relevant the thing they broke actually is to Solaris at this point, bug 665509 is so old it predates Firefox itself and goes back to the Mozilla suite days. I believe $(INSTALL) -t was wrong, and they meant $(NSINSTALL) -t because that makes more sense and is closer to what was there originally. It's what they have for WINNT, and it's possible a fix more like that could serve for Solaris as well. Alternatively, we could get rid of all these half-broken Makefiles and start building NSS with gyp files like Mozilla did. 3. I've completely cut out support for the Sun compiler and taken into account the reality that everyone builds Firefox (and therefore its forks) with GCC now on Solaris. This alone helped clean up a lot of the uglier parts of the code. 4. I've updated all remaining SOLARIS build flags to the newer XP_SOLARIS, because the SOLARIS flag is no longer set when building Solaris. 5. I've confirmed the workaround in gtxFontconfigFonts.cpp is no longer necessary. The Solaris people got impatient about implementing a half-baked patch for a fontconfig feature that wasn't ready yet back in 2009, and somehow convinced Mozilla to patch their software to work around it when really they should have just fixed or removed their broken fontconfig patch. The feature they wanted has since been implemented properly, and no version of Solaris still uses the broken patch that required this fix. If anyone had ever properly audited this code, it would have been removed a long time ago.
* | Issue #1257 - Part1: Remove watch class-hook and proxy trap.wolfbeast2019-10-26-19/+0
| |
* | Issue #1253 - Reset performance object on navigationwolfbeast2019-10-21-1/+13
|/ | | | | | | This also addresses clearing of document dependent JS slots which might get out of sync with innerWindow navigation; relevant comments added. This resolves #1253
* Issue #1222: Don't load plugin instances when they have no `src` URI.wolfbeast2019-09-01-0/+8
| | | | | | Favor fallback content in that case (if present). Fallback is always considered "good" in this case so may end up doing nothing which is what we'd want for corner cases that hammer this routine with no content.
* Issue #1179: fix indentationwolfbeast2019-09-01-3/+3
|
* Issue #1221: Pass the original element intowolfbeast2019-08-28-13/+46
| | | | | | | nsXMLContentSerializer::CheckElementEnd so that we can properly determine whether it has children. This resolves #1221
* Convert dom/base/nsImageLoadingContent.cpp to use AsyncOpen2 and followups ↵win7-72019-08-08-76/+119
| | | | | | along with it (1445670 and 1373780 part 2 and 3) Convert dom/base/nsImageLoadingContent.cpp to use AsyncOpen2 and followups along with it (1445670 and 1373780 part 2 and 3)
* Revert "Capture delayed events and cancel as necessary."wolfbeast2019-07-18-2/+2
| | | | | | | | | Tag #1052 (backout). Backed out for creating issues like #1191 and other issue-less problems with e.g. losing the caret from text boxes. Of note: this was also backed out from m-c for similar reasons in Bug 1332433. This fixes #1191. This reverts commit 3424afccaebc71c4acd4fa9eadf519c408c5965b.
* Consider domain when deciding on inner window reuse.wolfbeast2019-07-18-2/+1
|
* Dispatch a PluginRemoved event for actual plugins, not ↵win7-72019-07-14-2/+4
| | | | | | | | images/unknown/iframe-type <objects> If a page uses or removes many <object> elements which are not actually plugins, loading the page goes to a crawl because UXP recalculates the plugin UI every time. Only dispatch a PluginRemoved event for actual plugins.
* Attach FrameProperties to each frame instead of using a shared hashtablewin7-72019-06-26-1/+12
| | | | Dispense the shared hashtable and instead attach the frame property list directly to nsIFrame.
* NodeInfoManager should use a local cachewin7-72019-05-25-2/+32
| | | issue #1111
* Merge pull request #1115 from win7-7/NS_Atomize-cacheMoonchild2019-05-25-18/+20
|\ | | | | Add NS_Atomize cache for main thread use
| * change for nsNodeInfoManager.cppwin7-72019-05-25-1/+1
| | | | | | based to patch for https://bugzilla.mozilla.org/show_bug.cgi?id=1352235 v1 add main thread only cache.
| * Add missing NS_AtomizeMainThread(nameToUse);win7-72019-05-24-1/+1
| | | | | | nsCOMPtr<nsIAtom> nameAtom = NS_AtomizeMainThread(nameToUse);
| * add main thread only cache for nsIAtoms to speed up atomization dom/basewin7-72019-05-24-16/+18
| | | | | | add main thread only cache for nsIAtoms to speed up atomization
* | Issue #1102 - Disable <meta http-equiv=set-cookie>Gaming4JC2019-05-24-1/+2
|/ | | | Create a new pref 'dom.meta-set-cookie.enabled' which is set to 'false', disabling http-equiv meta cookies.
* Map IntersectionObserver rect to the correct viewport.wolfbeast2019-05-15-1/+2
| | | | | | | | | targetFrame is modified during the intersection computation loop, so it's not the viewport you want if there are scrollframes around. This bug triggers when IntersectionObservers are used on frames that wrap. Follow-up for #249.
* Capture delayed events and cancel as necessary.wolfbeast2019-04-26-2/+2
| | | | Tag #1052
* Issue #1053 - Drop support Android and remove Fennec - Part 1b: Remove ↵Matt A. Tobin2019-04-23-8/+3
| | | | MOZ_FENNEC
* Remove AIX VisualAge C++ compiler bug workaround.wolfbeast2019-03-31-17/+3
| | | | Tag #186
* Issue #187: Remove solaris conditional code.wolfbeast2019-03-30-4/+0
|
* Allow empty string on `location.search` setter.wolfbeast2019-02-12-4/+0
| | | | Fixes #970.
* Revert "Increase purple limit triggers for CC."wolfbeast2019-02-07-2/+2
| | | | This reverts commit babedf6c696f88734e59b63d0c6614962cc57519.
* Increase slice time for longer running CCs.Andrew McCreight2019-01-29-3/+14
| | | | | | | | | If a CC takes too long (around 50 slices) or gets interrupted by a GC, we have to finish it synchronously, which can cause a big pause. This patch tries to avoid that by eagerly increasing the slice budget the longer a CC goes on. It linearly increases the slice time from 5ms to 40ms as we approach the halfway point of a CC (1 second), matching GC pauses, and then leaves it at 40ms.
* Increase purple limit triggers for CC.wolfbeast2019-01-29-2/+2
| | | | | Making these much larger to allow more purple buffer buildup and prevent overzealous cycle collection on purple buffer pressure.
* Merge branch 'master' into cycle_collector-workwolfbeast2019-01-29-0/+10
|\
| * Actually unlink targets from registered intersection observers.wolfbeast2019-01-19-0/+10
| | | | | | | | | | | | | | When a node is released/removed, and it has an intersection observer attached to it, that observer should be unlinked at the time of release. This resolves #935.
* | Remove NS_IMPL_CYCLE_COLLECTION_TRAVERSE_SCRIPT_OBJECTSwolfbeast2019-01-18-37/+1
| |
* | Consolidate tracing and traversing.wolfbeast2019-01-18-1/+1
|/
* Rewrite IntersectionObserver list handling to be more robust.wolfbeast2019-01-18-8/+40
| | | | Tag #935.
* Add isIntersecting property to IntersectionObserverEntry.wolfbeast2019-01-17-0/+9
| | | | | | Per updated spec. This resolves the issue raised in #249.
* Telemetry: Remove stubs and related codeadeshkp2019-01-12-109/+0
|
* Align Element.ScrollIntoView() with the spec.wolfbeast2019-01-08-14/+53
| | | | | | | This also removes the (unused) shadow alias from nsIDOMHTMLElement which used the different calling convention. This resolves #927
* Fix crashiness of IntersectionObservers.wolfbeast2018-12-24-21/+25
| | | | Mozilla hashtables -still- suck.
* [intersection-observer] Calculate areas using int64_t.wolfbeast2018-12-22-4/+6
| | | | Tag #249
* Fix singed/unsigned type confusion for intersection threshold.wolfbeast2018-12-22-3/+3
| | | | Tag #249
* Use content area as the intersection rectangle ...wolfbeast2018-12-22-7/+11
| | | | | ... for custom root with overflow clip. Tag #249
* Map intersectionRect to the coordinate space of the target document.wolfbeast2018-12-22-7/+8
| | | | | | Spec says: "Map intersectionRect to the coordinate space of the viewport of the Document containing the target." Tag #249
* Use targetFrame->GetRectRelativeToSelf() as the initial intersection rect.wolfbeast2018-12-22-1/+1
| | | | Tag #249.
* Intersection ratio should be 1.0 for zero-area intersections.wolfbeast2018-12-22-1/+7
| | | | Tag #249
* Revise lifetime management of IntersectionObservers.wolfbeast2018-12-22-26/+46
| | | | Tag #249
* Issue #910 part 3. Throw SyntaxError from Location::SetProtocol on URI parse ↵wolfbeast2018-12-16-1/+4
| | | | failures.
* Issue #910 part 2. Strip ':' and anything following it from the string ↵wolfbeast2018-12-16-1/+8
| | | | passed to the location.protocol setter.
* Issue #910 part 1. Don't navigate when location.protocol is set to anything ↵wolfbeast2018-12-16-0/+17
| | | | other than http or https.
* Do not report resource-timing subdocument loads triggered by that subdocument.wolfbeast2018-12-14-0/+3
|
* Remove VR hardware support.wolfbeast2018-11-26-174/+0
| | | | This resolves #881
* Tell the cycle collector about nsScriptLoadRequest::mElement.wolfbeast2018-11-15-2/+10
| | | | Not doing this can cause a leak because there is a cycle between the load request and the script element.
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-08 19:36:20 +0000