* Exclude `.notranslate` and `[contenteditable]` elements from translation
The `.notranslate` class is used by Google Translate to skip certain elements. And for obvious reasons we should not be changing the contents of elements with `contenteditable` enabled. This will fix the issue with composing tweets on Twitter.
* fix linter
Co-authored-by: Jelmer van der Linde <jelmer@ikhoefgeen.nl>
* Import InPageTranslation updates from github.com/jelmervdl/firefox-translations
* Try to make the linter happy
* Add support for translating text nodes
This seems to be necessary for supporting Youtube. It also seems to fix the issue in #385, but I still see some interaction between the Wordpress plugin and this code that should not be happening.
* Decrease translation message batch size
The changes to InPageTranslation result in at least 50% less messages per page. To make the immediately visible elements render much quicker, I reduced it further to reduce the delay.
* Reuse text nodes from page
Reuse text nodes already existing in the page if possible. This fixes issues with React pages that tend to re-add text nodes if they have been removed, showing double or untranslated text. Fixes#405.
* Improve text deletion from errornously cloned inline elements
It worked in one direction, now it works in both. Still, this scenario should almost never happen.
# Conflicts:
# extension/view/js/InPageTranslation.js
* Let's treat `<a>` like `<span>`
# Conflicts:
# extension/view/js/InPageTranslation.js
* Warn about text nodes that become empty after translation
# Conflicts:
# extension/view/js/InPageTranslation.js
* Fix `removeTextNodes` call
* Make linter happy
to validate and publish metrics, per https://mozilla.github.io/glean/book/user/adding-glean-to-your-project/enable-data-ingestion.html#validate-and-publish-metrics
> After your product has been enabled, you must submit commits to probe scraper to validate and publish metrics. Metrics will only be published from branches defined in probe scraper's repositories.yaml, or the Git default branch if not explicitly configured. This should happen on every CI run to the specified branches. Nightly jobs will then automatically add published metrics to the Glean Dictionary and other data platform tools.
* Makes notificationBox compatible with Fx versions earlier than 93
* Adding tests for esr91
* Run mach bootstrap
* run mach bootstrap right after cloning
* Run both tests on same action
* Set MACH_USE_SYSTEM_PYTHON
* Restricit minimum fx version to what's compatible with the wasm nmt engine
* Capture and report wasm compilation errors
* Remove legacy loading for services object prior to Fx 88
Andre Natal
Tex2002ans
Chris Midgley
Evgeny Pavlov
Jelmer
Lonnen
Abhishek Aggarwal
Daniel Thorn
Gitoffthelawn