Commit graph

336 commits

Author SHA1 Message Date
athenian200
45bf760ac5 MoonchildProductions#1251 - Part 27: Fix ifdef style.
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.
2019-11-04 11:54:07 +08:00
athenian200
6de8a0f12d MoonchildProductions#1251 - Part 1: Restore initial Solaris support, fixed up.
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.
2019-11-04 11:52:13 +08:00
wolfbeast
3b9fbdc71d Issue #1257 - Part1: Remove watch class-hook and proxy trap. 2019-11-01 10:24:07 +08:00
wolfbeast
d21dc0f76a Issue #1253 - Reset performance object on navigation
This also addresses clearing of document dependent JS slots which might
get out of sync with innerWindow navigation; relevant comments added.

This resolves #1253
2019-10-25 12:00:08 +08:00
wolfbeast
b3b78fea06 Issue #1222: Don't load plugin instances when they have no src URI.
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.
2019-09-06 23:48:49 +08:00
wolfbeast
19a7a8f535 Issue #1179: fix indentation 2019-09-06 23:48:44 +08:00
wolfbeast
f34f8ca034 Issue #1221: Pass the original element into
nsXMLContentSerializer::CheckElementEnd so that we can properly
determine whether it has children.

This resolves #1221
2019-08-30 13:37:37 +08:00
win7-7
e6f376f5ef Convert dom/base/nsImageLoadingContent.cpp to use AsyncOpen2 and followups 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)
2019-08-10 06:26:08 +08:00
wolfbeast
d2baf53a14 Revert "Capture delayed events and cancel as necessary."
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.
2019-07-19 10:04:49 +08:00
wolfbeast
9a4b847b7e Consider domain when deciding on inner window reuse. 2019-07-19 10:04:47 +08:00
win7-7
ffb2d9d791 Dispatch a PluginRemoved event for actual plugins, not 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.
2019-07-19 10:04:08 +08:00
win7-7
922e819d1c Attach FrameProperties to each frame instead of using a shared hashtable
Dispense the shared hashtable and instead attach the frame property list directly to nsIFrame.
2019-07-05 21:32:14 +08:00
win7-7
53acd97766 NodeInfoManager should use a local cache
issue #1111
2019-05-31 07:19:14 +08:00
win7-7
f7def6729d change for nsNodeInfoManager.cpp
based to patch for https://bugzilla.mozilla.org/show_bug.cgi?id=1352235 v1 add main thread only cache.
2019-05-31 07:18:03 +08:00
win7-7
37870c0ff2 Add missing NS_AtomizeMainThread(nameToUse);
nsCOMPtr<nsIAtom> nameAtom = NS_AtomizeMainThread(nameToUse);
2019-05-31 07:17:59 +08:00
win7-7
c4af2549b2 add main thread only cache for nsIAtoms to speed up atomization dom/base
add main thread only cache for nsIAtoms to speed up atomization
2019-05-31 07:17:44 +08:00
Gaming4JC
4ab1401ee6 Issue #1102 - Disable <meta http-equiv=set-cookie>
Create a new pref 'dom.meta-set-cookie.enabled' which is set to 'false', disabling http-equiv meta cookies.
2019-05-31 07:17:21 +08:00
wolfbeast
78b6f639b2 Map IntersectionObserver rect to the correct viewport.
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.
2019-05-17 22:17:16 +08:00
wolfbeast
e3827df1a0 Capture delayed events and cancel as necessary.
Tag #1052
2019-04-27 08:56:22 +08:00
Matt A. Tobin
97059c1b48 Issue #1053 - Drop support Android and remove Fennec - Part 1b: Remove MOZ_FENNEC 2019-04-27 08:51:55 +08:00
wolfbeast
02260b18f3 Remove AIX VisualAge C++ compiler bug workaround.
Tag #186
2019-04-04 20:26:36 +08:00
wolfbeast
78d61fd2b1 Issue #187: Remove solaris conditional code. 2019-04-04 20:26:26 +08:00
wolfbeast
24fda598ca Allow empty string on location.search setter.
Fixes #970.
2019-02-16 00:28:18 +08:00
wolfbeast
a7680e43ed Revert "Increase purple limit triggers for CC."
This reverts commit babedf6c696f88734e59b63d0c6614962cc57519.
2019-02-16 00:28:13 +08:00
Andrew McCreight
7b5e5f85de Increase slice time for longer running CCs.
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.
2019-02-16 00:27:52 +08:00
wolfbeast
6cba36850f Increase purple limit triggers for CC.
Making these much larger to allow more purple buffer buildup
and prevent overzealous cycle collection on purple buffer pressure.
2019-02-16 00:27:50 +08:00
wolfbeast
39d5eb7759 Remove NS_IMPL_CYCLE_COLLECTION_TRAVERSE_SCRIPT_OBJECTS 2019-02-16 00:27:49 +08:00
wolfbeast
e015efb999 Consolidate tracing and traversing. 2019-02-16 00:27:47 +08:00
wolfbeast
7798af3c14 Actually unlink targets from registered intersection observers.
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.
2019-02-16 00:24:29 +08:00
wolfbeast
dc2cf8544d Rewrite IntersectionObserver list handling to be more robust.
Tag #935.
2019-02-16 00:24:21 +08:00
wolfbeast
9222116f26 Add isIntersecting property to IntersectionObserverEntry.
Per updated spec.

This resolves the issue raised in #249.
2019-02-16 00:24:20 +08:00
adeshkp
aea50f182f Telemetry: Remove stubs and related code 2019-02-16 00:24:04 +08:00
wolfbeast
14ea8bb121 Align Element.ScrollIntoView() with the spec.
This also removes the (unused) shadow alias from nsIDOMHTMLElement
which used the different calling convention.

This resolves #927
2019-02-16 00:24:00 +08:00
wolfbeast
304984a6aa Fix crashiness of IntersectionObservers.
Mozilla hashtables -still- suck.
2019-02-16 00:23:05 +08:00
wolfbeast
d76f949502 [intersection-observer] Calculate areas using int64_t.
Tag #249
2019-02-16 00:23:00 +08:00
wolfbeast
f82da789c8 Fix singed/unsigned type confusion for intersection threshold.
Tag #249
2019-02-16 00:22:59 +08:00
wolfbeast
d3a8693d52 Use content area as the intersection rectangle ...
... for custom root with overflow clip.
Tag #249
2019-02-16 00:22:57 +08:00
wolfbeast
475d865c14 Map intersectionRect to the coordinate space of the target document.
Spec says: "Map intersectionRect to the coordinate space of the
viewport of the Document containing the target."
Tag #249
2019-02-16 00:22:56 +08:00
wolfbeast
52f04699c0 Use targetFrame->GetRectRelativeToSelf() as the initial intersection rect.
Tag #249.
2019-02-16 00:22:54 +08:00
wolfbeast
47f52cee1f Intersection ratio should be 1.0 for zero-area intersections.
Tag #249
2019-02-16 00:22:53 +08:00
wolfbeast
42d9f2ffb3 Revise lifetime management of IntersectionObservers.
Tag #249
2019-02-16 00:22:51 +08:00
wolfbeast
4aacec4782 Issue #910 part 3. Throw SyntaxError from Location::SetProtocol on URI parse failures. 2019-02-16 00:22:31 +08:00
wolfbeast
a6eab2d84e Issue #910 part 2. Strip ':' and anything following it from the string passed to the location.protocol setter. 2019-02-16 00:22:29 +08:00
wolfbeast
32eb361301 Issue #910 part 1. Don't navigate when location.protocol is set to anything other than http or https. 2019-02-16 00:22:28 +08:00
wolfbeast
27d88fc505 Do not report resource-timing subdocument loads triggered by that subdocument. 2019-02-16 00:22:18 +08:00
wolfbeast
9b1124ccbd Remove VR hardware support.
This resolves #881
2019-02-16 00:20:27 +08:00
wolfbeast
b32338ed19 Tell the cycle collector about nsScriptLoadRequest::mElement.
Not doing this can cause a leak because there is a cycle between the load request and the script element.
2019-02-16 00:19:31 +08:00
wolfbeast
6e25ae612a Fix build bustage.
Tag #871
2019-02-16 00:19:29 +08:00
wolfbeast
a30b6ee962 Split the content viewer marking function in CCUncollectable out,
so a document-based marking function can be used separately.

Tag #871
2019-02-16 00:19:25 +08:00
wolfbeast
b7a342f120 Ensure user input suppression works correctly even after document.open. 2019-02-16 00:18:43 +08:00