The serializer needs to make each mailcite starts from head of a line.
However, mailcite may be a blocked `<span>`. So, its preceding `<br>`
is not required from the HTML point of view, but we need to preserve
it for the serializer.
If we need this hack in some other places, we should make
`HTMLEditUtils::GetFollowingUnnecessaryLineBreak()` aware of this
special handling in a follow up bug.
Differential Revision: https://phabricator.services.mozilla.com/D270784
When we find a block boundary, it may be current block's boundary or
other block's boundary. The lambda assume only the former, but the
STR of this bug hits the latter case.
So, when user modifies the text before a mail-quote which is a block of
`<span>` element should put `<br>` before it rather than end of it.
Differential Revision: https://phabricator.services.mozilla.com/D270782
It's used as the result in some cases. However, it's not tracked in
some cases when touching the DOM.
This modifies the API of `AutoTrackDOMPoint` to flush the tracking point
but can keep tracking. We should use the new API in every place later.
(This manually merges `WhiteSpaceVisibilityKeeper.cpp` because ESR140
still has the pref to take the legacy mode back and that blocks applying
the patch cleanly.)
Differential Revision: https://phabricator.services.mozilla.com/D270643
This patch updates browsertime's package files to fix the build failure due to the URL change for edgedriver.
This is needed to ensure browsertime dependencies can be installed (and not blocked by an outdated edgedriver)
when running raptor tests locally for the first time. The edgedriver issue does not seem to appear in CI
because browsertime tests in CI are currently using an older, cached browsertime-toolchain.
Updated the browsertime dependencies to version 24.8.2 and disabled perfstats for twitch-animation tests on the macOS 14.70 Shippable platform as a temporary fix for the perfstat failures that will be resolved in Bug 1972620. The usb-power-profiling package was also updated to 1.6.0 to avoid issues during symbolication when running the profiler. Previous browsertime dependency update to version 24.8.1 was failing on the firefox-constant-regression test.
Instead of downloading an archive from gitlab, which likes to send us a
bot challenge instead, just do a git clone, which should bring us the
same content.
This is somewhat unfortunate, but I couldn't find a better way to address this. There are two aspects to this fix:
1. In order for SVG chicklets to appear in the context menu the first time it is opened, we have to set an nsMenuX to be rebuilt in its constructor (bug 1923666). However, this interferes with some menus, such as the Window and the Edit menu, since macOS adds its own menu items to these menus. This patch expands the fix for bug 1939346 for the Window menu to also include the Edit menu, where the Emoji picker is added as a menu item.
2. Bug 1808223 addressed a regression due to a macOS bug where the emoji picker and the dictation menu item are added every time that a main menu bar is set for an app, but macOS 'forgets' to remove these items when switched away from one Firefox window to another and back again. One quirk about this is that if the user switches to another APP and back to the same Firefox window, macOS will not re-add these menu items to the edit menu again. So we need to avoid removing these problematic menu items in this situation. I was hoping to implement a fix that would simply remove duplicates *after* setting the `NSApp.mainMenu`, but if we do so then macOS will remove ALL added menu items and the emoji picker will disappear entirely from the Edit menu. So this appears to be the only way to properly fix this.
Differential Revision: https://phabricator.services.mozilla.com/D268239
When the RDD and GPU processes crashed simultaneously, we could get into
a position where we would try to recreate PVideoBridge between the RDD
and GPU processes, before bringing back up the RDD process. We should
now skip reinitializing the protocol if the RDD process is unavailable.
Original Revision: https://phabricator.services.mozilla.com/D175044
Differential Revision: https://phabricator.services.mozilla.com/D270327
The max-run-time is ignored by beetmover payload builders.
For signingscript, 10 minutes seems to be fine except for localized
notarization jobs, which started failing after scriptworker started
taking the payload's maxRunTime into account in v61.2.0.
Original Revision: https://phabricator.services.mozilla.com/D269539
Differential Revision: https://phabricator.services.mozilla.com/D269601
