This removes the testing enableServerWatcherSupport flag for indexedDB and cookies resources. As a consequence of this, some tests that were previously marked as failing on fission now pass, so they have been re-enabled as well.
Differential Revision: https://phabricator.services.mozilla.com/D113143
Automatic update from web-platform-tests
[idlharness.js] Simplify handling of inheritance and mixins (#28650)
Handling of these concepts was more complicated than (now) necessary.
No changes in the actual test results are intended.
Inheritance:
There's no reason to record inheritance separately in `IdlArray`'s
`this.["inheritance"]`, since it can be determined just as easily
from `this.members` via the `member.base` attributes.
The concept of "consequential interfaces" in Web IDL went away with
`implements` statements in https://github.com/heycam/webidl/pull/433
and here in https://github.com/web-platform-tests/wpt/pull/28619.
`traverse_inherited_and_consequential_interfaces()` can be replaced
with just `get_inheritance_stack()`.
While this changes the behavior of `default_to_json_operation()`, there
is no `toJSON` operation declared in a mixin in interfaces/, only in
resources/ tests, so this change should not affect real tests.
default_to_json_operation.html was updated along the lines of simplified
examples in the spec: https://github.com/heycam/webidl/pull/980
Mixins:
For valid `A includes B` statements, `A` is always an interface and
`B` is always an interface mixin, so there are no include chains or
the possibility of cycles. `recursively_get_includes()` assumed this.
Instead just save the `includes` statements found in `this.includes`
and apply them in `merge_mixins`, similar to partials.
The handling of partials isn't changed, but `collapse_partials` is
renamed to `merge_partials` to match the above.
Not today:
Further unification of partials and mixins is possible, and the handling
of [Exposed] is missing for mixins, but this is left for later.
--
wpt-commits: b1f27e8ebbac23edecd374e6ea23f3c395498822
wpt-pr: 28650
Automatic update from web-platform-tests
Web Share: Retire share-url-data-manual.https.html (#28654)
data: URLs are no longer supported by Web Share API.
https://github.com/w3c/web-share/pull/174
This is tested by automated tests.
The manual test in obsolete, it is not valid or needed.
closes#202
Co-authored-by: Eric Willigers <ericwilligers@chromium.org>
--
wpt-commits: 2eb3853c6bb77eed4a3b5de3b6042b72463efd65
wpt-pr: 28654
Automatic update from web-platform-tests
"justifyall" tests were the same as "justify" (#28459)
* "justifyall" tests were the same as "justify"; the last line wasn't aligned
* Choose a width that divides evenly with three or four boxes
Co-authored-by: Mike <mike@qtunes.org>
--
wpt-commits: bbcf0db171d766d92aeee5ed7d4e4359b1aeaf6c
wpt-pr: 28459
Automatic update from web-platform-tests
Improve assertion and comments for overflow-wrap-anywhere-011.html and its reference. (#28630)
Fixed#28614.
--
wpt-commits: dd806aec5821cbe9f20019943e97538ccd1d445a
wpt-pr: 28630
This test is for documentation purposes. You may run it locally on Windows by removing the skip-if = true from xpcshell.ini
As sharing folders on windows requires elevated priviledges, you will need to execute some commands in a separate cmd.exe instance with Admin priviledges.
Differential Revision: https://phabricator.services.mozilla.com/D113498
This internal pseudo-class used to be to highlight nodes in the
inspector, but the inspector no longer sets it. Now the only thing that
sets it is devtools/server/actors/accessibility/audit/contrast.js to
remove the text color / shadow from the test.
We should probably find another way to implement that that doesn't
misuse this pseudo-class (and then presumably remove this pseudo-class),
but for now this code is dead.
Differential Revision: https://phabricator.services.mozilla.com/D113371
If the editor instance is a `TextEditor`, the root element has to be
anonymous `<div>` element and it has only one text node when it has non-empty
value. Therefore, if it's in `TextEditor`, the method does not need to use
the complicated APIs for finding a text node from the anonymous `<div>` element
or padding `<br>` element since it can adjust the given point into the text
node without such API.
Differential Revision: https://phabricator.services.mozilla.com/D113240
Only the user is `EditorBase::BeginningOfDocument()` which is used by both
`TextEditor` and `HTMLEditor`. However, if it's a `TextEditor`, expected
result is only the first text node only when there is one. Therefore, we can
move it into `HTMLEditUtils` and make `EditorBase::BeginningOfDocument()`
find the text node by it self. Then, we can get rid of using
`EditorBase::GetEditorType()` in this case.
Differential Revision: https://phabricator.services.mozilla.com/D113239
They are instance members of `EditorBase` only for referring editor type and
editing host. Therefore, we can make them static with making them take
editor type and ancestor limiter as arguments.
Depends on D113236
Differential Revision: https://phabricator.services.mozilla.com/D113237
The following patches will get rid of inline wrapper methods of them.
Therefore, they shouldn't be called as "internal". And they return
`nsIContent*` instead of `nsINode*` so, `Get*Content()` is better name for
them.
Depends on D113229
Differential Revision: https://phabricator.services.mozilla.com/D113230
So, the meaning is reverted of this action. But with this change, the scanner
methods scans any nodes by default. This is simpler to understand from the
callers.
Depends on D113228
Differential Revision: https://phabricator.services.mozilla.com/D113229
Before moving them from `EditorBase`, they should take only one option argument
whose type is an `EnumSet` class.
Note that I wanted to name each option for optional behavior, but
`FindAnyDataNode` requires to revert the its meaning (I.e., only with this
patch, `true` should be set an option). Therefore, the following patch renames
it.
Differential Revision: https://phabricator.services.mozilla.com/D113228
We were adding the new shape to the table first, but this confused the pre-barrier
verifier. Likely a false positive because the shape is newly allocated.
We now add the entry to the table at the end, and if this fails we remove the
dictionary shape again. This also removes some unnecessary code for growing slots.
Differential Revision: https://phabricator.services.mozilla.com/D113493
It seems GTK downscales the cursor if the resolution is less than the
device scale, so this makes it consistent with X11 and all other desktop
platforms.
On the example on the bug it seems silly because the cursor is massive,
but on legit examples like:
https://downloads.scirra.com/labs/bugs/cursor-image-set/
This makes the cursor not abruptly change sizes when page zoom changes
for example.
Differential Revision: https://phabricator.services.mozilla.com/D113302
