This patch starts pinning Firefox to the Taskbar by default on all supported Windows versions. The main addition here is a port of our existing taskbar pinning code for modern Windows 10 & 11 versions to an NSIS plugin (compiled version also included).
After discussion with a few stakeholders, we also decided that we will never pin during an update on Windows 10 or 11. (Arguably we could stop on Windows 7 & 8 as well - but I don't really see any harm in carrying forward our pre-existing behaviour there.) With this in mind, I dropped all the second pinning attempt code (which was only ever enabled for Windows 10).
Differential Revision: https://phabricator.services.mozilla.com/D148288
This includes some minor updates to the desktop and Start Menu strings from Content Design as well.
I also removed the now-useless quicklaunch option (which was only used pre-Windows 7).
Differential Revision: https://phabricator.services.mozilla.com/D148289
This patch starts pinning Firefox to the Taskbar by default on all supported Windows versions. The main addition here is a port of our existing taskbar pinning code for modern Windows 10 & 11 versions to an NSIS plugin (compiled version also included).
After discussion with a few stakeholders, we also decided that we will never pin during an update on Windows 10 or 11. (Arguably we could stop on Windows 7 & 8 as well - but I don't really see any harm in carrying forward our pre-existing behaviour there.) With this in mind, I dropped all the second pinning attempt code (which was only ever enabled for Windows 10).
Differential Revision: https://phabricator.services.mozilla.com/D148288
There's a typo in the condition here, which results in returning CAIRO_INT_STATUS_UNSUPPORTED
in cases where that shouldn't be necessary. Fixing this gets me nice vector PDF output.
The bug is still present in upstream cairo trunk, so I'll report it there as well.
Differential Revision: https://phabricator.services.mozilla.com/D150381
The previous patch in this bug added crash annotations for the number
of total and currently active renderers. However, we are actually
interested in these values when the EGL surface creation fails, as
opposed to when we crash later on after failing to recover. This patch
adds the values to gfxCriticalNote at the time of the error.
Differential Revision: https://phabricator.services.mozilla.com/D150365
We get some intermediate state update when sourceTextContent is loading.
The goal is to reduce the calls to any CodeMirror API.
Differential Revision: https://phabricator.services.mozilla.com/D149896
Also stop passing `frame` to DebugLine which wasn't using this attribute.
This might prevent unnecessary component updates.
Differential Revision: https://phabricator.services.mozilla.com/D149895
We typically dispatch a PAUSED actions, with only the first frames,
and later dispatch FETCHED_FRAMES, with the full list of frames.
Avoid modifying the first one, which is typically the selected one
in order to avoid uncessary state changes.
Differential Revision: https://phabricator.services.mozilla.com/D149879
Now that we no longer have the intermediate "loading" object,
we can simplify the code checking for loading symbols by checking
if symbols are defined.
Differential Revision: https://phabricator.services.mozilla.com/D149856
This helps reduce the number of state changes and the number of renders.
We now switch from null symbols which means they are loading,
to an object with the loaded symbols.
Differential Revision: https://phabricator.services.mozilla.com/D149855
There is many props that are only relevant to the children components,
and we were calling expensive CodeMirror method on any prop change.
Differential Revision: https://phabricator.services.mozilla.com/D149853
browser_console_enable_network_monitoring.js is failing on beta because MBT is not enabled by default
so the the leagcy-listener copepath is used. This adds `chromeContext` to the network resource and fixes
the issue.
Differential Revision: https://phabricator.services.mozilla.com/D150328
This improves profiling with "perf" a bit because we now don't lose the Ion frame
anymore. It also lets us simplify the code because we can now use the frame pointer
instead of the stack pointer (less stable due to stack pushes).
Differential Revision: https://phabricator.services.mozilla.com/D150224
The main goal here is to get the wireframe test to work with
parent-controlled navigation.
This means we don't need to collect the wireframe any more in
PersistLayoutHistoryState, I think, because it is redundant.
I think we need to clear the wireframe in finish restore for
when we navigate back.
As a result of these changes, the two todo subtests in the
wireframe test now pass.
Differential Revision: https://phabricator.services.mozilla.com/D146252
This matches other browsers.
The scroll event is dispatched async, so
the test would mostly pass without the patch, actually, except for the
fact that we wouldn't scroll. So without the patch the test times out.
Differential Revision: https://phabricator.services.mozilla.com/D150237
We do not need a GBM device any more in child processes and in several
cases we're also not allowed to open it any more by the sandbox.
For remaining cases were we do need it in the parent process (the
fallback path in `SharedSurface_DMABUF::Create`, used for WebGL and the
experimental `widget.dmabuf-textures.enabled` feature, as well as in
`WaylandBufferDMABUF::Create` used by `gfx.webrender.compositor`), we
already call `Configure()` in `gfxPlatformGtk::InitDmabufConfig()` and set
`gfx::gfxVars::UseDMABuf` accordingly, making
`nsDMABufDevice::IsDMABufWebGLEnabled()` still return the correct value.
Differential Revision: https://phabricator.services.mozilla.com/D150324
In future, it won't be possible to specify clip hierarchy by the
old ClipId identifier, so convert these ones to clip-chains now.
Differential Revision: https://phabricator.services.mozilla.com/D150342
`AutoCompleteParent.getCurrentBrowser` was added bug 1573836. But formfill's
custom element uses actor directly now, so it is unused now.
Depends on D150081
Differential Revision: https://phabricator.services.mozilla.com/D150082
The chrome manifest flag parsing is not particularly flexible. It's
easiest to duplicate the manifest entries rather than further adjust
the parser.
Differential Revision: https://phabricator.services.mozilla.com/D149950
