SelectionStateChangedEvent is dispatched only by SelectionCarets. Hence
the removal. The modification in mochitest browserElement_CopyPaste.js
is effectively the reverting of [1] with AccessibleCaret enabled.
The DoCommandHelper is shell.js is removed as well, which handles the
'do-command' event dispatched from old text_selection_dialog.js in Gaia.
[1] https://bugzilla.mozilla.org/page.cgi?id=splinter.html&bug=1155493&attachment=8612154
DONTBUILD
--HG--
extra : amend_source : 1348306b0eee27ae08cef1b947e383dfded7798c
For test_bug648573.html and test_bug644768.html, we no longer need to
create an iframe to turn off the preferences. I move the content of
iframe.src back to the test files.
--HG--
extra : amend_source : eec926c474be934b99faeb604493c01c471066e7
All the files modified are straightforward deletion except TouchManager
and ZoomConstraintsClient. I add some includes and wrap TouchManager by
mozilla namespace to fix build errors due to the removal of TouchCaret.
SelectionStateChangedEvent is dispatched only by SelectionCarets. Hence
the removal. The modification in mochitest browserElement_CopyPaste.js
is effectively the reverting of [1] with AccessibleCaret enabled.
The DoCommandHelper is shell.js is removed as well, which handles the
'do-command' event dispatched from old text_selection_dialog.js in Gaia.
[1] https://bugzilla.mozilla.org/page.cgi?id=splinter.html&bug=1155493&attachment=8612154
--HG--
extra : commitid : GWwMqChxnUT
extra : source : 3f2c650804415aa98f42369bc2061ab2ada98661
extra : amend_source : b8f3a445248397f140723a07ea5bc85ed67d6054
For test_bug648573.html and test_bug644768.html, we no longer need to
create an iframe to turn off the preferences. I move the content of
iframe.src back to the test files.
--HG--
extra : rebase_source : 5cf321bf3280e032cc6645810e3e7faa7a6ff615
All the files modified are straightforward deletion except TouchManager
and ZoomConstraintsClient. I add some includes and wrap TouchManager by
mozilla namespace to fix build errors due to the removal of TouchCaret.
--HG--
extra : rebase_source : b31db322130f665e7dda53d1061cfc40f81ce411
The meaning of resource:///, resource://app/ and resource://gre/ needs to
remain constant. Unfortunately, the model of the resource protocol handler
is that it is possible to set substitutions that change their meaning.
So, we forbid setting overwriting the substitutions for those three
special "host names".
Unfortunately, with e10s, the full list of substitutions is also sent to
the content process, which then sets substitutions, making it harder to
know in which cases SetSubstitution is valid for those three "host names"
or not.
So instead of trying to find the right heuristics, use the recently added
SubstitutingProtocolHandler::ResolveSpecialCases API to handle the three
"host names" instead of storing them as "normal" substitutions.
Still actively reject SetSubstitution with the three special "host names"
so as to find issues such as bug 1224000 instead of allowing the chrome
manifest entry and have it silently ignored.
Skip some tests that time out with the fairly slow arm64 simulator. The listed
tests run on more than 100 seconds on my iMac.
Also reduce the number of JIT flag combinations tried in order to finish this
job in a reasonable time.
Andrea Marchesini
Ting-Yu Lin
Nigel Babu
philipp
Jim Mathies
Sotaro Ikeda
Masayuki Nakano
Jordan Lund
Tooru Fujisawa
Henry
Christoph Kerschbaumer
Jesse Ruderman
Brian Birtles
JW Wang
Randell Jesup
Sebastian Hengst
James Graham
Terrence Cole
Sean Stangl
Mike Hommey
Tom Schuster
Maja Frydrychowicz
Jakob Stoklund Olesen
Ehsan Akhgari
Wes Kocher