| Commit message (Collapse) | Author | Age | Lines |
... | |
| | |
|
| |
| |
| | |
add main thread only cache for nsIAtoms to speed up atomization
|
| |
| |
| | |
add main thread only cache for nsIAtoms to speed up atomization
|
|\ \
| | |
| | | |
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.
|
| |
| |
| |
| | |
Fixes #1092
|
|/
|
|
|
|
|
|
| |
* 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
|
|\
| |
| | |
Remove a stubbed telemetry function from app AUS.
|
| | |
|
|\ \
| | |
| | | |
Clicking a link with a target should open only 1 tab
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
- 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)
|
|\ \ \
| | | |
| | | | |
Support gzip-compressed SVGs in OpenType+SVG fonts
|
|/ / / |
|
|\ \ \
| |_|/
|/| | |
Enable double buffering when using XRENDER.
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| | |
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
|
|\ \
| | |
| | | |
Remove unboxed objects phase 1
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
| | | |
|
| | | |
|
| | | |
|
|\ \ \
| | |/
| |/| |
Issue #971 - Fix browser.link.open_newwindow functionality in Pale Moon
|
|/ / |
|
| |
| |
| |
| | |
Resolves #1096
|
| |
| |
| |
| |
| |
| | |
Self-hosted implementation that adds both functions and adds them to
@@unscopables as specced in ES2019.
Resolves #1095
|
| |
| |
| |
| | |
This resolves #1088
|
| |
| |
| |
| |
| |
| | |
This renames our internal function names because *Left and *Right might
be deprecated and have to be removed later, making that trivial.
Resolves #1089
|
|\ \ |
|
| | | |
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
|/
|
|
| |
Tag #21
|
|\
| |
| | |
When using XRENDER, create Xlib-based offscreen image surfaces.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| |
| |
| |
| |
| |
| |
| |
| | |
from nsMediaFragmentURIParser.h
This also magically makes Aero Peek work properly with Pale Moon thus:
Resolves #809
|
|\ \
| | |
| | | |
Update sync clear history function to use new clear() API call.
|
|/ / |
|
| |
| |
| |
| | |
windows have the AppMenu
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
Extension compatibility
|
|\ \
| | |
| | | |
Reader Updates
|
| | |
| | |
| | |
| | | |
tooltips r=Gijs,MarcoZ
|