Popup manager will eat click event when clicking outside of popup only if macOS
and Linux. This patch will add consumeoutesideclicks attribute to this popup in
order to prevent to react click event listener of a button which accessing to
this popup on all platform.
MozReview-Commit-ID: Sv3Hv9Olhn
--HG--
extra : rebase_source : 85bad58439dd9514acc6aac4977799f102777026
With the updated OnThread method SetInputListener method cannot continue asserting for being in audio callback. This check is not realistic since it is used on a newly created driver before being started.
MozReview-Commit-ID: 5gntuHm3fnr
--HG--
extra : rebase_source : e3bc17e9d8c83c4d61686889af41edfb3ef3902f
These two methods assert for OnGraphThreadOrNotRunning when their callers assert for OnGraphThread. Since the second assert is more limited we do not have to assert for a wider eventuality.
MozReview-Commit-ID: 2cgzO160l6F
--HG--
extra : rebase_source : 922a3d9775bb25022e456c19495b5e1666e7f8b7
The class has been enhanced to store the thread id at the beginning of the callback and use it in order to compare with the current thread id when OnThread method is called. The old mechanism which includes the mInCallback flag has been removed.
MozReview-Commit-ID: DWSbFQfvKzX
--HG--
extra : rebase_source : e6c011da563b8f1d562ca7a394433e1e53fcffa4
User prompt tests request new sessions and as such force the
browser to restart way more often. Extra delays due shutdown
and startup times of the browser are expected, and to better
handle timeouts and failures these tests should be located in
their own module.
Therefore this patch moves all existing tests which validate the
correct user prompt handling to a user_prompts.py file located
in the same sub folder of the corresponding command.
MozReview-Commit-ID: 2Nd8IRByzQd
--HG--
rename : testing/web-platform/meta/webdriver/tests/fullscreen_window/fullscreen.py.ini => testing/web-platform/meta/webdriver/tests/fullscreen_window/user_prompts.py.ini
rename : testing/web-platform/meta/webdriver/tests/get_active_element/get.py.ini => testing/web-platform/meta/webdriver/tests/get_active_element/user_prompts.py.ini
rename : testing/web-platform/meta/webdriver/tests/get_element_attribute/get.py.ini => testing/web-platform/meta/webdriver/tests/get_element_attribute/user_prompts.py.ini
rename : testing/web-platform/meta/webdriver/tests/get_element_property/get.py.ini => testing/web-platform/meta/webdriver/tests/get_element_property/user_prompts.py.ini
rename : testing/web-platform/meta/webdriver/tests/get_element_tag_name/get.py.ini => testing/web-platform/meta/webdriver/tests/get_element_tag_name/user_prompts.py.ini
rename : testing/web-platform/meta/webdriver/tests/get_title/get.py.ini => testing/web-platform/meta/webdriver/tests/get_title/user_prompts.py.ini
rename : testing/web-platform/meta/webdriver/tests/get_window_rect/get.py.ini => testing/web-platform/meta/webdriver/tests/get_window_rect/user_prompts.py.ini
rename : testing/web-platform/meta/webdriver/tests/is_element_selected/selected.py.ini => testing/web-platform/meta/webdriver/tests/is_element_selected/user_prompts.py.ini
rename : testing/web-platform/meta/webdriver/tests/maximize_window/maximize.py.ini => testing/web-platform/meta/webdriver/tests/maximize_window/user_prompts.py.ini
rename : testing/web-platform/meta/webdriver/tests/minimize_window/minimize.py.ini => testing/web-platform/meta/webdriver/tests/minimize_window/user_prompts.py.ini
extra : rebase_source : 52694ff27ee1f1f1d46376fd94d2653f8bebd3fc
Tests for a specific command have to use a shared function
for each of the included tests of a module to avoid redefinition
of the same code.
In a follow-up patch those shared methods could even be
separated out as fixtures for each of the sub folders.
MozReview-Commit-ID: 11lAp7J8IoZ
--HG--
extra : rebase_source : c8168b4c42ff177d1b4247478c6058f72f3f1db3
We occasionally get reports of UI unresponsiveness immediately following the
download phase of the stub installer. The longest operation that runs on the
main thread during this phase is validating the code signature of the full
installer. This patch moves that work (which is done in a native NSIS plugin)
to a separate thread. Hopefully this helps resolve the hangs.
I've also converted the build files for the plugin from Visual C++ 6 to 2017,
just to avoid the inconvenience of needing to pull up VC6 to build it.
MozReview-Commit-ID: CKje2a8M62i
--HG--
extra : rebase_source : ec9a11268eed3c4f9e0783532b0e910289e809f9
That method is used on update of channelCount constraint. By raising a ControlMessage to MediaStreamGraph we avoid the lock the mutex on a non priority thread. Unfortunately we have to send the message in main thread first, thankfully this will change soon.
MozReview-Commit-ID: 8JRSmKGGVAN
--HG--
extra : rebase_source : 3d3a3f03ec601e5fbe0e8fda01608ee8cadf8d78
Restructuring of the existing code no functional change.
MozReview-Commit-ID: JWaa8LgG4MR
--HG--
extra : rebase_source : 97190b870172549a0cd2453078c0511887059b73
Restructuring of the existing code no functional change.
MozReview-Commit-ID: FARNItrajfD
--HG--
extra : rebase_source : 0887c6546bb43538e32b99950e2febca77a32bfb
This commit introduces a new highlighter. This highlighter is specialized in
highlighting text-runs in a page that use a specified font.
The highlighter is based on a platform API that returns Range objects.
Therefore, the approach I chose was to simply feed these objects to the
window Selection object. This way, we get highlighting for free without
having to create any markup in the content page.
The drawback is that the highlighting looks different than in other places
of DevTools.
However it's most probably way better in terms of performance, and will
adapt natively to edge cases like APZ, scrolling, CSS transform, etc.
This commit also has a simple UI: on mouseover of a font name in the font
inspector panel, corresponding text runs are highlighted in the page.
This UI is hidden behind a pref for now, so we can test the feature with
some chosen users and gather feedback to improve the UI before shipping.
Finally, an integration test was added.
MozReview-Commit-ID: Fu3t0b5kbdy
--HG--
extra : rebase_source : 80493e64ad6fdb1ec1963021eb9bd7c3f5398201
Use `E10SUtils` to check for cases where browser code would try to force a
browser to reselect a new process (such as when it is a preloaded browser) so
that we can avoid any process changes once RDM is open.
If such a case applies, navigate to about:blank first to trigger the process
change before starting RDM.
MozReview-Commit-ID: CxspLFXXotF
--HG--
extra : rebase_source : cb94789344f17c0b51ff4afbb54921218a2dd1b5
Extract logic around whether a browser needs to change processes, get a new
frameloader because of preloading, etc. from `_loadURI` in `browser.js` to
`E10SUtils.jsm` where it can be shared with other code paths.
The side effect paths (trying to handle in chrome, removing preloaded state) are
left behind in `browser.js` so that the `E10SUtils` version can be a pure
function.
MozReview-Commit-ID: 6LYB3e3U5o8
--HG--
extra : rebase_source : d6ecac045f90e62a374f8a100e3cc8e1f45f7527
We bump the Mercurial version after a new Mercurial release. 4.6 was
just released. So...
MozReview-Commit-ID: LQ49eVCDuGG
--HG--
extra : rebase_source : 6b213a62216d1b8a9ec4f303d05d01e0609734a1
The clip chain API in webrender allows us to build the clip state in WR
so that it matches the gecko display list more closely. This patch throws
away ScrollingLayersHelper.* and introduces ClipManager.* which pushes
the clip state to WR using the new method. A quick summary of the new
method is below.
Each display item in gecko has a DisplayItemClipChain which is a chain
of individual clips. The individual clips are defined in WR, and the
clip ids for those clips are put into a WR clip chain using the new
define_clip_chain API. Furthermore, each clip chain can also have a
parent chain, which is used to link a DisplayItemClipChain to the parent
display item's DisplayItemClipChain. This allows the WR clip state to
closely match the structure of the gecko display list clip state,
resulting in more correct behaviour.
There are a few other major changes that are lumped into this patch and
that were tricky to separate into their own patches:
- The collapsing of WrScrollId and WrStickyId into WrClipId. On the WR
side all the clip ids are treated the same anyway. Trying to preserve
the arbitrary distinction on the gecko side was resulting in
increasingly convoluted code, with different kinds of Variant<..>
types in the method signatures. It was much simpler and resulted in a
bunch of code deletion to just collapse the types.
- Moving the "override" mechanism from WebRenderAPI to ClipManager. The
override mechanism (explained in ClipManager.h) was simplified by
moving it into ClipManager, because it removed the need for tracking
additional clip stack state in WebRenderAPI.
MozReview-Commit-ID: GGbdFyJGprK
--HG--
extra : rebase_source : baa56ff179e917b0ab5a5c186a3a415761f8050a
This is a refactoring that moves the "parent clip id" determination from
bindings.rs into WebRenderAPI.cpp. This should be functionally
identical.
MozReview-Commit-ID: 36rQmsH5E7J
--HG--
extra : rebase_source : f376e71f7681ec3f67e0ab4f2e3035da4edf2a5b
On Desktop and GeckoView we only ever need to store histograms for a
subsession and clear the histograms when a snapshot is done (e.g. a main ping is built).
On Fennec we don't have subsessions and only store for a session and never clear the storage.
MozReview-Commit-ID: BeVi86kZPs2
--HG--
extra : rebase_source : 50bb218c9fb9a04c8d60d6300e4e9e67544232c0
This reestablishes the separtion between wptserve and the rest of web-platform-tests.
It moves the parts of the configuration that are specific to wpt out into the
serve.Config class. It also removes the default.config.json file and just puts
the default configuration directly into the code since there it is able to use
things like runtime paths without difficulty.
MozReview-Commit-ID: FXAClJ8JJof
--HG--
rename : testing/web-platform/tests/tools/sslutils/__init__.py => testing/web-platform/tests/tools/wptserve/wptserve/sslutils/__init__.py
rename : testing/web-platform/tests/tools/sslutils/pregenerated.py => testing/web-platform/tests/tools/wptserve/wptserve/sslutils/pregenerated.py
Automatic update from web-platform-testsFile API: lastModifiedDate has been obsolete for a while
--
wpt-commits: 95127fa5adb1d9953899561c152c518c552e4ed0
wpt-pr: 10821
Julian Descottes
Mantaroh Yoshinaga
yulia
Dão Gottwald
Gijs Kruitbosch
Alex Chronopoulos
Henrik Skupin
Matt Howell
Martin Robinson
Kartikaya Gupta
Brad Werth
arthur.iakab
Patrick Brosset
J. Ryan Stinnett
Gregory Szorc
Jan-Erik Rediger
Ted Mielczarek
Aki Sasaki
Raul Gurzau
Dorel Luca
Christoph Kerschbaumer
Samuel Thibault
Yuri Khan
Jason Duell
Coroiu Cristina
Ryan VanderMeulen
Ben Kelly
moz-wptsync-bot
James Graham
Guido Urdaneta
Anne van Kesteren