Fix-ups in this patch:
* Enable multidex on messaging example apps to fix Lite build bustage where we API 16 is still supported
* Switch from deprecated assertThat to Hamcrest version
* Remove usage of deprecated ExpectedException.none()
Differential Revision: https://phabricator.services.mozilla.com/D178819
Adds functionality to the following menuitems:
always-translate language will immediately translate
the page if not already translated.
never-translate language will hide the translations
button and restore the page if translated.
never-translate site will hide the translations
button and restore the page if translated.
Depends on D177860
Differential Revision: https://phabricator.services.mozilla.com/D178512
Adds tests for all of the menuitems in the Translations
panel settings menu, including always-translate-language,
never-translate-language, and never-translate-site.
Depends on D177859
Differential Revision: https://phabricator.services.mozilla.com/D177860
Adds functionality for the never-translate-site
menuitem in the Translations panel settings menu.
When active, translations will not be offered for
this website.
Depends on D177858
Differential Revision: https://phabricator.services.mozilla.com/D177859
Adds functionality for the never-translate-language
menuitem in the Translations panel settings menu.
When active, translations will not be offered for
websites in this language.
Depends on D177857
Differential Revision: https://phabricator.services.mozilla.com/D177858
Adds functionality for the always-translate-language
menuitem in the Translations panel settings menu.
When active, websites will auto-translate for that
language.
Depends on D177856
Differential Revision: https://phabricator.services.mozilla.com/D177857
Adds new menuitems to the Translations panel settings
menu for always translate language, never translate
language, and never translate site.
Depends on D177855
Differential Revision: https://phabricator.services.mozilla.com/D177856
Adds a new button and panel for managing Translations
settings to the about:preferences panel.
Manages always-translate languages, never-translate
languages, and never-translate sites.
Depends on D178228
Differential Revision: https://phabricator.services.mozilla.com/D177854
Copies the code for Translation exceptions in about:preferences
to new files to preserve the git-blame history so that they can be
modified in a subsequent patch
Depends on D178723
Differential Revision: https://phabricator.services.mozilla.com/D178228
Skips a test that is causing intermittent failures in CI, which
tests functionality that is not part of the Translations MVP.
Differential Revision: https://phabricator.services.mozilla.com/D178723
Chrome for Windows does not dispatch `keydown` event for shortcut keys existing
from the fullscreen mode. Therefore, we can follow it.
For reserving only shortcut keys in fullscreen mode, we need to duplicate XUL
`<key>` elements which define the shortcut keys (only one in Windows/Linux,
but 3 in macOS). Then, their `disabled` attributes should be managed when
toggling the fullscreen mode.
Finally, we need to make `XULKeySetGlobalKeyListener` check the `disabled`
attribute **of** `<key>` elements because it's check in `DispatchXULKeyCommand`
in the final step:
https://searchfox.org/mozilla-central/rev/11a4d97a7b5cdfa133f4bda4525649f651703018/dom/events/KeyEventHandler.cpp#315-316
and it stops handling everything with doing nothing. I'm not sure whether this
was intentionally implemented or just a inefficient code which we didn't take
care the performance. However, I think that ignoring the disabled `<key>`
elements is reasonable behavior from `<key>` element users point of view.
(I found only one `<key>` which is disabled by default:
https://searchfox.org/mozilla-central/rev/11a4d97a7b5cdfa133f4bda4525649f651703018/browser/base/content/browser-sets.inc#225-233)
Differential Revision: https://phabricator.services.mozilla.com/D178262
I don't see why this would stop being relevant. We want to continue having
historical information on this even if we're not actively looking at it today.
Differential Revision: https://phabricator.services.mozilla.com/D178688
The EditorEventListener for HTMLEditor is registered on document,
which is problematic because it can't receive events when the focus is
switched between elements in the same shadow tree due to shadow dom
encapsulation.
We fix this by moving the EditorEventListener to nsWindowRoot so the
events can always be received.
Differential Revision: https://phabricator.services.mozilla.com/D178215
Set the `--enable-change-array-by-copy` shell flag and the
`javascript.options.experimental.enable_change_array_by_copy` pref to true
by default in all builds.
Remove the `--enable-change-array-by-copy` build flag from `js/moz.configure`
and make all code previously guarded by `#ifdef ENABLE_CHANGE_ARRAY_BY_COPY`
compile unconditionally.
Remove `change-array-by-copy` from testing build configurations (non262
and jit-test tests are no longer guarded with
`getBuildConfiguration()['change-array-by-copy']`
Remove all code from test config files that sets
`javascript.options.experimental.enable_change_array_by_copy`; only
`StaticPrefList.yaml` should set this pref.
Fix non262 unscopables test that apparently wasn't running before to use
the correct names for change-array-by-copy methods
Remove the `TypedArray` property from `gPrototypeProperties` in
`test_xrayToJS.xhtml`, as this property was written but never read.
Differential Revision: https://phabricator.services.mozilla.com/D174699
Add `ORB_BLOCK_REASON` to learn more about the reasoning of orb blocking in the wild.
Add ORB_BLOCK_INITIATOR to learn about the initiators. We can add more probes in the future if we want to target a specific initiator.
Differential Revision: https://phabricator.services.mozilla.com/D178102