We already had focus changing tests covered by
_test_focus_obtained_by_long_press(). This patch adds tests for focus
not being changed from an editable element after long-pressing on a
non-selectable element.
These tests will fail after reverting this change.
"Bug 1197739 - Do not change focus too early unless the frame is selectable"
https://hg.mozilla.org/mozilla-central/rev/4f2822bbbdb2
--HG--
extra : transplant_source : %26%E8%BAx%D2y%3DS%5BvLH%0Fy%11N%2B%D9%3B%E0
Errors thrown by takeScreenshot used to be silently ignored. When the
command started using the new dispatching technique in bug 1202663,
it was surfaced we do not support taking screen captures of SVG documents.
Since this is a requirement for Web Platform Tests, this patch corrects
the wrong assumptions about document body and document element.
This patch also significantly refactors the screen capture code, but
only uses the new implementation in contnent space, since some further
modifications are required to use it in chrome.
r=dburns
r=jgriffin
--HG--
extra : commitid : DdCIEpd5PEJ
extra : rebase_source : 7357010f992d7f995765c685000892cc59d9ec9a
The screen capture tests were not testing that the screenshots are of
what they're meant to be of. In order to confidently fix bug 1202663,
these new tests will ensure we do not have any regressions.
r=jgriffin
r=dburns
--HG--
extra : commitid : AulnylZMj6Y
extra : rebase_source : c2604e0e3bf1a975b1f35a149ef7f2bdb08840de
The screen capture tests were not testing that the screenshots are of
what they're meant to be of. In order to confidently fix bug 1202663,
these new tests will ensure we do not have any regressions.
r=jgriffin
--HG--
extra : commitid : GkRPL9uVwjG
extra : rebase_source : 594ea1655f61552d430c3242e6b3418e550c27b3
is called. r=ato
This means that we are now doing step 7 in
http://w3c.github.io/webdriver/webdriver-spec.html#get
--HG--
extra : commitid : KQi5f9c0C1r
extra : rebase_source : 9c77a1d9aadf529ddbae2d32e0e1f9c4d532e181
extra : histedit_source : f40f377e1398f72fa68efd69ad864d9e4ae7e2b4
* Incorporate the for-loop in python into javascript so that we only
need to call execute_script() once.
* Add documentation for parameters.
--HG--
extra : commitid : 88Mi3beYfSI
extra : rebase_source : bcf949c8a6055cf6ccaf541f8005fe88256555be
The version numbers have been moved to be major.minor.patch to allow
better versioning moving forward.
--HG--
extra : commitid : Lm21l6zZmge
extra : rebase_source : 432a27f8727106a78114b745aca019771f254e93
Add get_pref(), set_pref(), set_prefs() to make manipulate preferences
easier.
enforce_gecko_prefs() did the similar job as set_prefs(), but it will
restart the browser if a preference to be set are different from what is
already set in the system. Not all gecko preferences require a restart
to work. Using set_prefs() should make testing faster. See bug 1048554.
--HG--
extra : commitid : 8zY9oaHkSW1
extra : rebase_source : 787114d94f50e9f132fb7d5898cecf104e281700
This test sends keys to the urlbar causing a page navigation, then waits on
the current url to confirm the navigation is reflected. Because the navigation
changes remoteness, the url check and loading the content listener in the
new process race. When the url check wins, it causes a hang by sending a
message before the frame script to receive it loads.
This is a very specific scenario that only impacts tests that need to cause
navigation to in-process pages with key events. If these sort of tests
become a priority, this will need to be revisited.
--HG--
extra : commitid : LRu93romh31
In a following patch, all DevTools moz.build files will use DevToolsModules to
install JS modules at a path that corresponds directly to their source tree
location. Here we rewrite all require and import calls to match the new
location that these files are installed to.
--HG--
extra : commitid : F2ItGm8ptRz
extra : rebase_source : b082fe4bf77e22e297e303fc601165ceff1c4cbc
The findChildElement and findChildElements commands were originally
added to provide Selenium compatibility because it sends an "id" field
in the body.
They are both unneeded now that we have wires which extracts the element
ID from the URI template and sets the "element" field that the normal
findElement and findElements commands use.
r=dburns
--HG--
extra : commitid : 9UOUJoukHH1
extra : rebase_source : 2f848ebbfa69b82b03d718340b8203d9183083d6
When a TEXTAREA element is focused it returns the cursor to the last
position was at, or places it last. INPUT @type="text" (or any other
textual input element) places the caret at the beginning. Because of
this we move the caret to the end of the input field. The next time
the element is focussed, the cursor should move to the end.
The layout touch caret tests relied on the caret being left in its
previous position. This patch addresses that by using the advanced user
interaction API for these test cases.
r=jgriffin
--HG--
extra : commitid : 7tchyrqIp00
extra : rebase_source : 5f164dc051183056c92a2da7fb6e601fff748b29
