Bug 1561465 - Remove ELOG. r=nalexander, a=jcristau The condition that enabled ELOG to do something has been broken since bug 279212 landed two years ago, because MAKEFLAGS doesn't contain the dash for flags, so looking for "-s" never did anything. Bug 1560527 changed the condition to !BUILD_VERBOSE_LOG, which as of the previous commit, does work. This would restore the old behavior, at the expense of build time, since it involves wrapping in a shell script, which is not necessarily desirable (and hasn't been done for two years now) Differential Revision: https://phabricator.services.mozilla.com/D35967

Bug 1561465 - Avoid being too verbose after bug 1560527. r=nalexander, a=jcristau Bug 1560527 was not supposed to change verbosity for mach build, but it turns out it did, because the ifeq it copied from one place to another was wrong in the first place. While here, replace a ifeq that did work with the now equivalent BUILD_VERBOSE_LOG. Differential Revision: https://phabricator.services.mozilla.com/D35966

Bug 1559946 - The CFR FxA Bookmark Panel Message has incorrect dimensions in some locales. r=r1cky, a=jcristau Differential Revision: https://phabricator.services.mozilla.com/D35676

Bug 1519940 - Use keyboard_handle_keymap instead of keys-changed on wayland. r=stransky, a=jcristau If OnKeysChanged was called after keyboard_handle_keymap, then our newly configured keymap would be immediately cleared again. In order to avoid such scenario, use only keyboard_handle_keymap on wayland. Differential Revision: https://phabricator.services.mozilla.com/D32599

Bug 1558393 - Don't keep top level scope owner when going backwards. r=smaug, a=jcristau When going backwards the host is the last thing of the scope we see, not the first, so we need to make sure to properly switch to the document scope. To be clear, the order this is happening when bogusly going backwards from `second` to `first` is: * We're doing frame traversal so start off the <div>. * The text is the first frame in preorder we find, we figure out that the current top-level owner is the host. But it's not focusable so we carry on. * Now we go to the next frame and find the <span>. `oldTopLevelScopeOwner` is still the span itself, and we don't change it (that's what my patch fixes), so we go into the "We're within non-document scope, continue", and thus skip trying to focus the host. With this fix we actually realize that the current top level scope owner has changed and thus don't skip it and try to focus the slot properly. Differential Revision: https://phabricator.services.mozilla.com/D35585

Bug 1530660: Fix registration for nsSafeFileOutputStream. r=erahm, a=jcristau Differential Revision: https://phabricator.services.mozilla.com/D35490

Bug 1348503 - Retrieve the FrameLayerBuilder pointer from the LayerManager when we need it. r=tnikkel, a=jcristau Differential Revision: https://phabricator.services.mozilla.com/D34772

Bug 1547624 - Start inactive Layer building during ProcessDisplayItems so that any contained hit-test info gets propagated to the outer Layer before we add the next item. r=miko a=jcristau Differential Revision: https://phabricator.services.mozilla.com/D32261

Bug 1547624 - Update mScaledHitRegionBounds when we add hit-test info to a Layer from within an inactive Layer. r=miko a=jcristau Differential Revision: https://phabricator.services.mozilla.com/D32260

Bug 1560587 - Remove incorrect event redirection. r=tnikkel, a=jcristau In this codepath, the parent process may be sending an event to a particular content process. The last-saved mouse target might be stale, and using that to redirect the event can result in the event getting sent to the wront content process. Deleting this erroneous change restores correct behaviour. Differential Revision: https://phabricator.services.mozilla.com/D35697

Bug 1561245 - Add a null check for the received Intent; r=VladBaicu, a=jcristau According to the documentation - https://developer.android.com/reference/android/app/Service.html "The Intent supplied to Context.startService(Intent) may be null if the service is being restarted after its process has gone away, and it had previously returned anything except START_STICKY_COMPATIBILITY." We will ignore the case when the system restarts our Service as we only expect it to be properly started by us, in the event of a crash. Differential Revision: https://phabricator.services.mozilla.com/D35790

Bug 1551458 Back button won't go back in history (Pixel 3 XL(Android 9)). r=VladBaicu, a=jcristau Created an exception in the key event suppression mechanism for the back button KEYCODE. Differential Revision: https://phabricator.services.mozilla.com/D33950

Merge esr68 to beta. a=merge

Automatic version bump CLOSED TREE NO BUG a=release DONTBUILD

No bug - Tagging dead08d3f55c81b333abee35ff42e5856904aebe with FENNEC_68_0b13_RELEASE a=release CLOSED TREE DONTBUILD

No bug - Tagging dead08d3f55c81b333abee35ff42e5856904aebe with FENNEC_68_0b13_BUILD1 a=release CLOSED TREE DONTBUILD

no bug - Bumping Firefox l10n changesets r=release a=l10n-bump DONTBUILD be -> a7b895a610b8 bn -> 3ec0ef1ed685 cs -> 3c50db528527 da -> 6d5111c773d1 de -> 9815376b1116 eo -> a5aad3ac227b et -> 08b5c171a842 eu -> f1c75294ff2f fi -> 908e9a6d9473 fr -> 67595a57d831 gn -> fcf0f98962c3 hi-IN -> 9543b38f9f11 id -> 8716389a5063 is -> 05776085158e it -> b4f976f51043 ja -> b362c42d6963 ja-JP-mac -> 946c255c788a ka -> 821b1290f578 kab -> 04252d7305aa kk -> 333d143d524f ko -> c80216856b31 nb-NO -> d75c0bb81fac nl -> 62b5e5894454 nn-NO -> a0edc259dd68 oc -> caa3cebc09b5 pt-BR -> a79b96f6e05d ro -> c12c336fa521 sl -> ee8e0ff66300 sq -> fc654a093500 th -> c2255a706fe0 tr -> 756c48113ac4

no bug - Bumping Fennec l10n changesets r=release a=l10n-bump DONTBUILD be -> a7b895a610b8 bn -> 3ec0ef1ed685 cs -> 3c50db528527 da -> 6d5111c773d1 de -> 9815376b1116 eo -> a5aad3ac227b et -> 08b5c171a842 eu -> f1c75294ff2f fi -> 908e9a6d9473 fr -> 67595a57d831 gn -> fcf0f98962c3 hi-IN -> 9543b38f9f11 id -> 8716389a5063 is -> 05776085158e it -> b4f976f51043 ja -> b362c42d6963 ka -> 821b1290f578 kab -> 04252d7305aa kk -> 333d143d524f ko -> c80216856b31 lo -> c3a37fc5682b nb-NO -> d75c0bb81fac nl -> 62b5e5894454 nn-NO -> a0edc259dd68 oc -> caa3cebc09b5 pt-BR -> a79b96f6e05d ro -> c12c336fa521 sl -> ee8e0ff66300 sq -> fc654a093500 th -> c2255a706fe0 tr -> 756c48113ac4

No bug - Tagging da9f01df3bef6c8e34104875b4c5453b59e63155 with FIREFOX_68_0b13_RELEASE a=release CLOSED TREE DONTBUILD

Automatic version bump CLOSED TREE NO BUG a=release DONTBUILD

No bug - Tagging da9f01df3bef6c8e34104875b4c5453b59e63155 with DEVEDITION_68_0b13_RELEASE a=release CLOSED TREE DONTBUILD

Backed out changeset 1d577a6a7cd1 (bug 1560600) for build bustages. a=backout

Bug 1545421 - New nsresult error codes for 407, 502 and 504 http response codes returned by proxies + test, r=dragana a=jcristau Differential Revision: https://phabricator.services.mozilla.com/D32817

Bug 1528082: Add an environment variable to disable dedicated profiles for enterprise use. r=froydnj a=jcristau In some situations dedicated profile support does not work well. This includes a handful of linux distributions which always install different application versions to different locations, some application sandboxing systems as well as enterprise deployments. This environment variable provides a way to opt out of dedicated profiles for these cases. Differential Revision: https://phabricator.services.mozilla.com/D35249

Bug 1560600 - Don't allow WebRender for AMD on non-nightly for non-Windows platforms. r=kats a=jcristau Differential Revision: https://phabricator.services.mozilla.com/D35569

No bug - Tagging da9f01df3bef6c8e34104875b4c5453b59e63155 with FIREFOX_68_0b13_BUILD1 a=release CLOSED TREE DONTBUILD

No bug - Tagging da9f01df3bef6c8e34104875b4c5453b59e63155 with DEVEDITION_68_0b13_BUILD1 a=release CLOSED TREE DONTBUILD

No bug - Manually bump the Fennec Beta version number. a=release

Bug 1555627 - Set a learn more link on net error pages. r=prathiksha a=ritu Bug 1284835 removed the hard-coded learn more link on cert and net error pages, which worked for cert error pages because they explicitly set their own learn more links, but net error pages were relying on the default href to be set. This wasn't revealed until bug 1530348 made about:neterror part of the new error pages. The solution is simply to explicitly set the correct learn more link to net error pages. Note that in the case of PR_END_OF_FILE errors, we were not previously showing a "learn more" link. That was not intentional, as far as I can tell, but was caused by the bug fixed in bug 1477875. Differential Revision: https://phabricator.services.mozilla.com/D35163

Bug 1559317 - ensure outline is not visible when tbody gets focus on :active. r=mtigley a=ritu Depends on D35065 Differential Revision: https://phabricator.services.mozilla.com/D35066