Because of modifications to the DataTransfer constructors, the status of the tests that use DataTransfer objects had to be changed to reflect the fact that those tests now pass. Additionally, a test had to be deleted because it tested an obscure situation using the old Chrome only constructor.
MozReview-Commit-ID: LOWuPwh0NeW
We expose the relevant APIs on textarea and input elements anyway
(chromeonly). The QIs will throw on a non-input or non-textarea element, but
none of these consumers expect that to happen.
The DoMouseClick helper is also removed because no other caller can now pass a null aEvent. Other MouseClicked implementations are also updated since aEvent cannot be null, which was already the case.
MozReview-Commit-ID: 3bTJ6cZW9ZA
--HG--
extra : rebase_source : ae1bafe7144f6f428e2ef4e7047d5c64e0a19e8c
This aligns the markup of the base "arrowscrollbox" binding with the "clicktoscroll" derived binding, while still keeping different event handlers.
MozReview-Commit-ID: 9eYt1kyjgP9
--HG--
extra : rebase_source : 16600f0916ac4188ceaf8dff61fb61021cc8da5a
This series exposes an existing bug in nsFindIterator where it cannot rewind
into NAC properly. This nested iterator setup is going to change heavily as part
of making it work on Shadow DOM, so just punt on this for now.
MozReview-Commit-ID: Aq8XfXjQw6f
There are some places where we have a thing which may not even be a node, and
we end up hardcoding the value of DOCUMENT_NODE there, because
"foo.nodeType == foo.DOCUMENT_NODE" will test true if foo is not a node: both
sides will be undefined.
This series exposes an existing bug in nsFindIterator where it cannot rewind
into NAC properly. This nested iterator setup is going to change heavily as part
of making it work on Shadow DOM, so just punt on this for now.
MozReview-Commit-ID: Aq8XfXjQw6f
Fairly straightforward, just a blanket removal. Haven't heard
anything on dev-platform or fx-data-dev regarding this removal,
so I think it's likely safe to remove on Nightly, and we can
revert if anyone makes a fuss.
As part of removing the HangMonitor, I renamed a few things and
reorganized the namespaces to not depend on a HangMonitor
namespace. Hopefully this doesn't produce too much noise in the
diff, it just seemed appropriate to move everything around
rather than keep dangling vestiges of the old system.
MozReview-Commit-ID: 8C8NFnOP5GU
--HG--
extra : rebase_source : a8840bd26f4b01b756ffa72345ababb625048550
They're extending xul:box, which is a tag which, like textbox, doesn't have any
special treatment in layout, so should not impact anything. Try does look
happy about this.
MozReview-Commit-ID: A7q0VGTS4kf
--HG--
extra : rebase_source : 021c0510cf1a51074219979ba658a9c40d32c83f
This is fairly straightforward, other than the fact that the
nomenclature gets a bit awkward with the aForce parameter on
the ForcePaint methods. I'm not sure which direction to go with
this - "aForce" seems a fairly intuitive name for what we want,
and I'm kind of inclined to say the existing ForcePaint mechanic
should be renamed to something like PaintWithInterrupt, or
PaintWithPriority.
MozReview-Commit-ID: Bj9DROug1pC
--HG--
extra : rebase_source : a3d91fec940d83325d36bafb13fe892e9c9530e8
This is a partial backout of Bug 1347791 part 3; a5fbb7e2d1d0.
a5fbb7e2d1d0 added a mediaBlocked attribute to the browser element, which
tracked whether the tab has ever been in the foreground, so that this could
be saved and restored in session restore. We don't session restore this
anymore, so we can remove this attribute and associated event handlers.
This also removes the media.autoplay* pref accesses which are accounted for in
the test browser_preferencecs_usage.js, so remove those prefs from that test.
MozReview-Commit-ID: HLeylLzEsW8
--HG--
extra : rebase_source : 3b169c324b4a0c5163151805d9fcdb0b90a37517
Also fixes existing code which fails the rule.
MozReview-Commit-ID: CkLFgsspGMU
--HG--
extra : rebase_source : 86a43837659aa2ad83a87eab53b7aa8d39ccf55b
Having the native theme widget to flip its own direction turned out to be
something not needed anymore, and it interfere with the CSS rule we set to
flip non-native SVG background.
This patch turned that off and always flips the resizer with CSS transform.
MozReview-Commit-ID: EbjTfFpJpZ0
--HG--
rename : layout/reftests/forms/textarea/resize-ref.html => layout/reftests/forms/textarea/resize-rtl-ref.html
rename : layout/reftests/forms/textarea/resize.html => layout/reftests/forms/textarea/resize-rtl.html
extra : rebase_source : a319698cea6c8460aaed23948e20b0757cec686e
This loads a JS file to register the Custom Element whenever XUL documents
get created. This is a pattern we plan to follow for future elements as well -
stringbundle is just an easy target to prove it out with.
MozReview-Commit-ID: 7PlisCknrKW
--HG--
rename : toolkit/content/widgets/stringbundle.xml => toolkit/content/widgets/stringbundle.js
extra : rebase_source : 5bf94038556c9b956de3678cd4bc817f5d837f45
