Add a new `test_init` subcommand to wrench that tests for successful
initialization. This can then be used in combination with the
`--precache` flag to ensure that all shaders are compiled
successfully. Run this with and without `--use-unoptimized-shaders` to
ensure that both variants of the shaders compile.
For android we need to ensure that wrench terminates the process when
it completes successfully otherwise it will run forever. We also must
ensure that the test harness stops the old process before relaunching
the activity one in the case of a timeout.
Depends on D109773
Differential Revision: https://phabricator.services.mozilla.com/D109774
They are slated to ride the trains starting with this cycle (Gecko 89).
@font-face metrics override is only enabled in Nightly and controlled by the
preference layout.css.font-metrics-overrides.enabled (added in bug 1681691).
Differential Revision: https://phabricator.services.mozilla.com/D109651
BrowserTestUtils.promiseAlertDialog and friends account for commonDialog.xhtml,
but not other dialogs which go through gDialogBox. This fixes that by adding a
inWindowDialog option to promiseAlertDialog. I don't like this solution very
much - it requires all of these dialogs to fire the event themselves. An
alternative might be putting this code in some file which these all include,
but given how small the code is that feels like overkill. Alternatives welcome.
Differential Revision: https://phabricator.services.mozilla.com/D109674
This variable can be used by platforms to modify the current directory, useful
on Android as the process where the xpcshell test runs does not really have the
concept of CWD.
Differential Revision: https://phabricator.services.mozilla.com/D106207
This variable can be used by platforms to modify the current directory, useful
on Android as the process where the xpcshell test runs does not really have the
concept of CWD.
Differential Revision: https://phabricator.services.mozilla.com/D106207
This patch changes the value of an empty `<input type=file>` control as obtained from the `FormData` API, which used to be an empty string, to be a `File` object with empty contents, whose name is the empty string and whose type is `"application/octet-stream"`.
Differential Revision: https://phabricator.services.mozilla.com/D106605
This test had a number of issues that were preventing it from passing in any
browser. After this patch, it passes in Firefox at least, and I suspect it'll
pass in other browsers as well.
Problems with the test that are fixed here (all of which were keeping this test
from passing):
- The descriptive text on the page was different ("box." vs "area"), between
the testcase and reference case.
- The testcase had a margin on this text, for no clear reason.
- The reference case had a border around the scaled-up green div, whereas
the testcase doesn't (making them mismatch by the size of that border).
And while I'm at it, I'm making minor edits...
- making the indentation more consistent.
- switching to the HTML5 standards-mode doctype (since the testcase isn't
doing anything relevant to quirks-mode that would require a legacy doctype).
- removing the unused ".hidden" CSS rule from the reference case.
This makes the testcase and reference case more usefully diffable.
Differential Revision: https://phabricator.services.mozilla.com/D109524
These `.ini` files only include a line to enable the pref media.mediasource.enabled, but that pref is always true by default in the wpt environment, so we don't need those files anymore.
Differential Revision: https://phabricator.services.mozilla.com/D109554
This patch changes the value of an empty `<input type=file>` control as obtained from the `FormData` API, which used to be an empty string, to be a `File` object with empty contents, whose name is the empty string and whose type is `"application/octet-stream"`.
Differential Revision: https://phabricator.services.mozilla.com/D106605
Those command handlers just check whether the given editor is an `HTMLEditor`
or not. Therefore, we should make them check whether the given editor is
a single line editor or not instead.
Differential Revision: https://phabricator.services.mozilla.com/D108572
Although these commands supported supported only by Gecko, we shouldn't stop
supporting them unless we know the usage in the wild. Therefore, this patch
adds the handling code for `TextEditor` too.
Differential Revision: https://phabricator.services.mozilla.com/D108571
Currently, `Document` checks it only with whether the document is editable
or not. Only with this check, `execCommand` and the other related methods
work only when there is `contenteditable`.
Therefore, this patch makes it to check whether the target is editable or not
with target editor.
Differential Revision: https://phabricator.services.mozilla.com/D108570
For making `execCommand` and related methods with `<input>` and `<textarea>`
even if they are in `contenteditable` and focused, command should be handled
in active editor (focused editor if in foreground window and tab).
However, some commands should be handled by `HTMLEditor` even if an `TextEditor`
has focus. Therefore, this patch adds new enum class which have 3 state into
`InternalCommandData` and makes `AutoEditorCommandTarget` consider it with the
enum class.
Note that the new failures about `contentReadOnly` command will be fixed by
a following patch.
Differential Revision: https://phabricator.services.mozilla.com/D108569