Android sets dom.disable_window_showModalDialog to true in mobile.js so this
test now fails because it explicitly sets the pref to false. For the time
being, it's easiest to simply skip this test on Android and turn it back on
once we remove the test entirely.
MozReview-Commit-ID: 5XsiXupESvg
--HG--
extra : rebase_source : 8d176e069aac5cc49ec06b7055be5a81b45c188a
Annoyingly, setting the pref doesn't magically make the function appear on the
current window, so we create an iframe and retrieve it from there.
MozReview-Commit-ID: 9fOr4YJOzXh
--HG--
extra : rebase_source : d23643b388538955cc831a3b6e1473232ab5498a
This patch is for the intermittent bug 1357082 which has a failure in the test 'test_pointerlock-api.html' and is more frequent when it is run on Ubuntu 16.04. This failure is resolved by retrying the mouse movement until it actually occurs.
MozReview-Commit-ID: 9XC4zmWj8Gn
--HG--
extra : rebase_source : 8f2d80661f8da82a68eeade2261a2d729c13c84d
Discussion at <https://github.com/whatwg/dom/issues/319>. In short, the
specification used to say to throw sometimes InvalidCharacterError and
sometimes NamespaceError, but browsers disagreed on which to throw in
corner cases, and everyone agreed it wasn't worth the effort to spec the
distinction, so we just changed it to InvalidCharacterError across the
board.
The test changes are already upstream.
MozReview-Commit-ID: AWSZBznQprG
--HG--
extra : rebase_source : 2f0051f48124380f17300a38ceb8c2ab23015ca1
Other browsers do not support any of these (IIRC), telemetry reports
essentially zero usage, and supporting them is contrary to the DOM spec.
Notes on specific events:
CommandEvent and SimpleGestureEvent: These are not supposed to be
web-exposed APIs, so I hid the interfaces from web content too
(necessary to avoid test_all_synthetic_events.html failures).
DataContainerEvent: This was a non-standard substitute for CustomEvent
that seemed to have only one user, so I removed it entirely and switched
the user (MozillaFileLogger.js) to CustomEvent.
ScrollAreaEvent: This is entirely non-standard, but we apparently expose
it deliberately to web content, so I didn't see any reason to remove it
from createEvent.
SimpleGestureEvent and XULCommandEvent: Can still be created from
createEvent(), but not by content.
TimeEvent: This is still in because it has no constructor, so there's no
other way to create it. Ideally we'd update the SMIL spec to add a
constructor. I did remove TimeEvents.
MozReview-Commit-ID: 7Yi2oCl9SM2
--HG--
extra : rebase_source : 199ab921acfc531b8b85e77f90fcd799b03c887b
The dialog functionality of the non-standard window.find API has been broken
with e10s since it shipped, and bug 1182569 or bug 1232432 (or both) have
broken it for non-e10s.
This patch remove showDialog support entirely, for both e10s and non-e10s,
in a more deliberate way. We now ignore the argument.
MozReview-Commit-ID: 1CTzgEkDhHW
--HG--
extra : rebase_source : 9aa9623ef649fb2c42ad22738130c361acf6b8cc
The dialog functionality of the non-standard window.find API has been broken
with e10s since it shipped, and bug 1182569 or bug 1232432 (or both) have
broken it for non-e10s.
This patch remove showDialog support entirely, for both e10s and non-e10s,
in a more deliberate way. We now ignore the argument.
MozReview-Commit-ID: 1CTzgEkDhHW
--HG--
extra : rebase_source : 02b5b7ce3852d2254016b384f29f2a84063a4957
I looked at the wrong try push before pushing this change to inbound. Backing it
out hopefully before it turns too many pushes orange.
MozReview-Commit-ID: 5cREsyfWrmb
Blake Kaplan
Stone Shih
Michael Layzell
Matt Woodrow
Peter Van der Beken
Carsten "Tomcat" Book
Greg Mierzwinski
Brad Werth
Ehsan Akhgari
Yoshi Huang
Daosheng Mu
Ryan VanderMeulen
Mats Palmgren
Andrea Marchesini
Ben Kelly
Wes Kocher
btian
Edgar Chen
Tim Taubert
Aryeh Gregor
Tobias Schneider
Mike Conley
Tom Tung
Florian Queze
Sebastian Hengst