summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeLines
* Avoid some useless ForgetSkippable handling while we're already dealingwolfbeast2019-05-25-0/+5
| | | | with snow-white objects.
* [IndexedDB] Call SendFailureResult if the actor has been destroyed.wolfbeast2019-05-25-20/+26
| | | | | | | | | | Normally we wouldn't need to send any notifications if the actor was already destroyed, but it can be a VersionChangeOp which needs to notify its parent operation (OpenDatabaseOp) about the failure. So SendFailureResult needs to be called even when the actor was destroyed. Normal operations redundantly check if the actor was destroyed in SendSuccessResult and SendFailureResult, therefore it's ok to call it in all cases here.
* [js, ARM] Always check error return from BufferOffset::diffB.Lars T Hansen2019-05-25-2/+10
| | | | | | | We were missing error checks at two points. In one case an error return is meaningful; in another case it is not, as the problem should have been guarded against at a higher level by emitting far jump islands soon enough during pasteup of compiled code.
* [libpng] Backport an upstream libpng patch.wolfbeast2019-05-25-2/+1
|
* Make nsFind::Find handle empty string searches.wolfbeast2019-05-25-0/+5
|
* Merge pull request #1115 from win7-7/NS_Atomize-cacheMoonchild2019-05-25-21/+74
|\ | | | | 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);
| * make HTML parser to use faster atomization in main threadwin7-72019-05-24-1/+1
| |
| * remove unnecessary spaceswin7-72019-05-24-4/+0
| |
| * add main thread only cache for nsIAtoms to speed up atomization xpcom/dswin7-72019-05-24-2/+57
| | | | | | add main thread only cache for nsIAtoms to speed up atomization
| * 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
* | Merge pull request #1114 from g4jc/disable-meta-cookieMoonchild2019-05-25-17/+32
|\ \ | | | | | | Disable <meta http-equiv=set-cookie>
| * | Issue #1102 - Disable <meta http-equiv=set-cookie>Gaming4JC2019-05-24-17/+32
|/ / | | | | | | Create a new pref 'dom.meta-set-cookie.enabled' which is set to 'false', disabling http-equiv meta cookies.
* | Fix architecture flag for PPC64wolfbeast2019-05-25-1/+1
| | | | | | | | Fixes #1092
* | Lots of time spent maintaining nsDisplayLayerEventRegions (#1116)win7-72019-05-24-0/+4
|/ | | | | | | | * Simplify the dispatch-to-content region Simplify the dispatch-to-content region in nsDisplayLayerEventRegions::AddFrame() and AddInactiveScrollPort() if it starts to get large. * tabs to spaces
* Merge pull request #1099 from adeshkp/remove-telemetry-funcMoonchild2019-05-24-11/+0
|\ | | | | Remove a stubbed telemetry function from app AUS.
| * Remove a stubbed telemetry function from app AUS.adeshkp2019-05-22-11/+0
| |
* | Merge pull request #1105 from FranklinDM/pm_uri_tabbrowser-workMoonchild2019-05-24-2/+13
|\ \ | | | | | | Clicking a link with a target should open only 1 tab
| * | Issue #1104 - Pass an opener to loadOneTab in the openURI functionFranklinDM2019-05-23-1/+3
| | |
| * | Issue #1104 - Set the browser's opener when adding a new tabFranklinDM2019-05-23-1/+10
| | | | | | | | | | | | | | | - This modifies `loadOneTab` and `addTab` to accept an opener - This code was adapted from Basilisk's copy of tabbrowser.xml without the refactored code changes (which is a lot more involved as it divides addTab's functions into multiple functions)
* | | Merge pull request #1108 from g4jc/svg_opentypeMoonchild2019-05-24-0/+69
|\ \ \ | | | | | | | | Support gzip-compressed SVGs in OpenType+SVG fonts
| * | | Issue #1101 - Support gzip-compressed SVGs in OpenType+SVG fontsGaming4JC2019-05-23-0/+69
|/ / /
* | | Merge pull request #1100 from Ionic/bugfix/xrender-flickerMoonchild2019-05-22-1/+14
|\ \ \ | |_|/ |/| | Enable double buffering when using XRENDER.
| * | Enable double buffering when using XRENDER.Mihai Moldovan2019-05-22-1/+14
|/ / | | | | | | | | | | | | | | | | This fixes flickering/bars/stripes showing up during quickly-updating operations on Intel hardware when using XRENDER. For more information, refer to the code comment. See #1061
* | Merge pull request #1091 from MoonchildProductions/remove-unboxedMoonchild2019-05-22-1511/+102
|\ \ | | | | | | Remove unboxed objects phase 1
| * | Remove Unboxed Objects from vm/ - Part 2wolfbeast2019-05-16-64/+17
| | |
| * | Remove unboxed object code from jit, Part 1wolfbeast2019-05-16-627/+26
| | |
| * | Remove Unboxed Objects from vm/ Part 1 + fix deprotwolfbeast2019-05-16-15/+10
| | |
| * | Remove array headerwolfbeast2019-05-16-1/+0
| | |
| * | Remove unboxed object code from iteration.wolfbeast2019-05-15-32/+10
| | |
| * | Remove unboxed objects from GCwolfbeast2019-05-15-118/+3
| | |
| * | Remove Unboxed Objects in ScalarReplacementwolfbeast2019-05-15-112/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | A note about the Scalar Replacement Changes: The M{Load,Store}Unboxed* instructions in theory could be used to manipulate and analyze typed arrays. However, TypedArrays should already be excluded from eligibility because of the potential for cross-thread sharing in a SharedArrayBuffer world, and so the only support in Scalar Replacement here is for Unboxed Objects, meaning it can all be removed.
| * | Remove initial chunk of Unboxed Objects machinery part 2wolfbeast2019-05-15-12/+0
| | |
| * | remove unboxed code chunk (wip1)wolfbeast2019-05-14-507/+25
| | |
| * | Unhook Unboxed Objects optionwolfbeast2019-05-13-24/+12
| | |
* | | Merge pull request #1097 from FranklinDM/pm_external_sametab-workMoonchild2019-05-22-1/+0
|\ \ \ | | |/ | |/| Issue #971 - Fix browser.link.open_newwindow functionality in Pale Moon
| * | Issue #971 - Fix browser.link.open_newwindow functionality in Pale MoonFranklinDM2019-05-22-1/+0
|/ /
* | Implement Symbol​.prototype​.descriptionwolfbeast2019-05-20-0/+33
| | | | | | | | Resolves #1096
* | Implement array.flat and array.flatMapwolfbeast2019-05-19-1/+120
| | | | | | | | | | | | Self-hosted implementation that adds both functions and adds them to @@unscopables as specced in ES2019. Resolves #1095
* | Add nullcheck.wolfbeast2019-05-17-0/+4
| | | | | | | | This resolves #1088
* | Implement String.prototype.trimStart and trimEnd.wolfbeast2019-05-17-16/+22
| | | | | | | | | | | | This renames our internal function names because *Left and *Right might be deprecated and have to be removed later, making that trivial. Resolves #1089
* | Merge branch 'master' of https://github.com/MoonchildProductions/UXPwolfbeast2019-05-15-3/+2
|\ \
| * | Fix scroll bar orientation on MacOSwicknix2019-05-15-3/+2
| | |
* | | 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.
* / Rip broken telemetry out of the app AUS.wolfbeast2019-05-14-736/+1
|/ | | | Tag #21
* Merge pull request #1060 from Ionic/bugfix/scrolling-regressionMoonchild2019-05-13-8/+5
|\ | | | | When using XRENDER, create Xlib-based offscreen image surfaces.
| * When using XRENDER, create Xlib-based offscreen image surfaces.Mihai Moldovan2019-04-27-8/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Mozilla tried to enable XRENDER support with backends other than Cairo in 286348:e13aaaaf1962 / https://hg.mozilla.org/mozilla-central/rev/e13aaaaf1962 - at least until they decided to completely remove XRENDER support. The change looked innocent enough, but actually turned out to do exactly the opposite: it forcefully enabled image offscreen surfaces with GTK2 when it was previously disabled (since gfxPrefs::UseImageOffscreenSurfaces() will always return true) and, by extension, disabled the XRENDER-based functionality by creating a non-Xlib surface. Interestingly, a previously enabled double buffering check was also disabled by this, but since the comment for this was diverging with the code, that behavior just sounds like yet another bug. Instead of disabling image offscreen surfaces (at least when using the GTK2 backend), let's force the creation of Xlib-based image surfaces when XRENDER support is enabled. This will let UXP use the more common/modern code paths, but also make scrolling much faster again. Too fast scrolling may induce tearing (if not smoothed), but on the other hand performs much better in remote computing contexts. As an added benefit, GTK3-based builds should roughly behave the same way. Further tests with the GTK3-backend enabled will be required in the future.
* | Remove deprecated appending of #-moz-resolution from Pale Moon and left over ↵Matt A. Tobin2019-05-12-17/+3
| | | | | | | | | | | | | | | | from nsMediaFragmentURIParser.h This also magically makes Aero Peek work properly with Pale Moon thus: Resolves #809
* | Merge pull request #1086 from zootboy/masterNew Tobin Paradigm2019-05-12-1/+1
|\ \ | | | | | | Update sync clear history function to use new clear() API call.
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-20 13:08:44 +0000