https://github.com/w3c/uievents/issues/112
This is supported by all other UAs. In the past we had compatibility
problems when trying to add support, but it seems these might be fixed
if we make all arguments optional beyond the first.
The interface chosen for the method is from the spec, which has been
updated to match Chrome. This is also very similar to WebKit, but the
final four arguments are different from IE.
MozReview-Commit-ID: 36AeX1JwJTt
--HG--
extra : rebase_source : 28b298d370f0f9a5ab4090a71a2aae91f1d90025
Add a triangle next to the ping selection button that emphasize the
to the current ping selection popup state.
MozReview-Commit-ID: GOzv01S0i9h
--HG--
rename : browser/themes/shared/icons/arrow-dropdown-12.svg => toolkit/themes/shared/icons/arrow-dropdown-12.svg
rename : browser/themes/shared/icons/arrow-dropdown-16.svg => toolkit/themes/shared/icons/arrow-dropdown-16.svg
extra : rebase_source : d94fe7aa872cd6912263179cac1004b335c0973a
Introduce a new make command to produce new type of language packs based
on web extensions.
MozReview-Commit-ID: EltYtzT7ZRR
--HG--
extra : rebase_source : 6477be07c747e90992f18d8c7bff93fd48965200
Per spec, getSelection() should return null when the document is not
associated with a browsing context.
MozReview-Commit-ID: B6QbLWVmfcF
--HG--
extra : rebase_source : 4826ba52726ac413bc8c4b95cc309da7ce7986ab
The spec puts it on the Document interface, not HTMLDocument, so it
should apply to XML documents as well. In general we want APIs to be
available for all types of documents unless there's a specific reason
not to.
Tests submitted upstream:
https://github.com/w3c/web-platform-tests/pull/6804
MozReview-Commit-ID: A0QDxpONNCE
--HG--
extra : rebase_source : 0c84863b455c3e9748aedcfb562920f8679e358c
On Taskcluster machines, /tools/buildbot doesn't exist. It turns out, nothing
refers to exes['python'] anyway, so we can just remove that (the preference is
to use sys.executable instead).
The references to exes['buildbot'] were all for sendchanges from builds to
tests, and those too are all gone now.
Lines like
'virtualenv': ['/tools/buildbot/bin/python', '/tools/misc-python/virtualenv.py'],
Were committing two sins: first, using a python executable from a random
virtualenv; and second, using a virtualenv.py from another random directory (in
this case, it's a utility script for a PuppetAgain module). Such lines are
replaced with a reference to /tools/virtualenv/bin/virtualenv, which is
installed for the express purpose of providing a virtualenv binary on testers
(for builds, we use the vendored copy).
MozReview-Commit-ID: 4iHX3B3MLyK
--HG--
extra : rebase_source : e4b4902a19d688b148c136bd10c706fc127cbf2d
As stated by Philipp, the prefs engine (PREFS_GUID) accesses Services.appinfo at import time.
Changed code to use a lazy getter on the global object instead.
changed services/sync/modules/engines/prefs.js
MozReview-Commit-ID: 1MAGKM9r1OM
--HG--
extra : rebase_source : 37f3112383f8073d1afa220ff7e8ac4d7fc38ec5
There was an error because of the console.dir call, which is calling
the server to fetch the properties of the inspected object.
But, since the console.dir call was the last command to be called,
the actor were cleared before the properties fetch call was done,
resulting in an error on the server (no such actor for ID).
To fix this, we wait for the properties fetch call to be done
before closing the tab.
MozReview-Commit-ID: 9bsh3vHVPVa
--HG--
extra : rebase_source : 4e9e40d2811ab8dd69872ba060654f5061aa01c9
This commit:
- Makes the window controls have exactly the same height as tabs when the
menubar is hidden, and have the same height as the menubar when it is shown.
This requires us to remove the menubar height before flushing layout in
case it is shown, since we need its original height for the calculation.
- Removes the top margin between the menu bar and the window border
that was present on Windows 10 and makes it apply on Windows 7 only.
The border was causing miscalculations of the window control height,
which could have been handled in browser-tabsintitlebar.js, but since
it's not part of the Photon spec we decide to remove it entirely.
- Makes window control height calculations ignore vertical tabs toolbar
margins. The only margin it has right now is -1px and the calculation
code doesn't work right with negative margins.
MozReview-Commit-ID: HJXxUUJFX8x
--HG--
extra : rebase_source : d5e741cc4ca897ef125ab3e807bc009cd540ade6
This test was failing because we need to set an additional
pref to make our Windows 10 test infra support touch events,
and because some elements it was testing got renamed.
MozReview-Commit-ID: 4h2YxFzRrGp
--HG--
extra : rebase_source : 588eab64df3235fe66641c5ba398ac95c3abfe3b
