This reverts commit 1faeaa00f5.
Revert "Bug 1959727 - Implement ShadowRoot.setHTML and share more code. r=emilio"
This reverts commit 3a84b03088.
Revert "Bug 1959727 - Add the sanitizer option to parseHTMLUnsafe. r=emilio" for causing wpt failures in Document-parseHTMLUnsafe.html
This reverts commit 17ced5ec89.
This reverts commit 0681b181d6.
Revert "Bug 1932150 - Fix lint failure" for causing Build bustage.
This reverts commit 60cc0878d3.
Revert "Bug 1932150 - Add new test cases for selection in flat tree r=smaug"
This reverts commit 3dbe5fc183.
Revert "Bug 1932150 - Make selection code to correctly iterate flattened tree r=smaug"
This reverts commit 6f7a1e4886.
Revert "Bug 1932150 - ContentSubtreeIterator #3: Fix a bug in ContentSubtreeIterator where the end container is in the light DOM of a shadow host r=jjaschke"
This reverts commit 19ce2c5806.
Revert "Bug 1932150 - ContentSubtreeIterator #2: Allow ContentSubtreeIterator to iterate nodes in flattened tree r=jjaschke"
This reverts commit d9d192bc3a.
Revert "Bug 1932150 - ContentSubtreeIterator #1: Make the end container related logic in ContentSubtreeIterator more robust r=jjaschke,smaug,dom-core"
This reverts commit 2fbde5b84d.
Revert "Bug 1932150 - Update ranges to correctly set and update nodes for flattened selection r=jjaschke,smaug,dom-core"
This reverts commit 116d26c37f.
Revert "Bug 1932150 - Allow using flat tree order for point comparing in selection r=jjaschke,smaug,dom-core"
This reverts commit 2ba73e1639.
Revert "Bug 1932150 - Fix some inconsistency about indicating whether the selection is allowed to cross the shadow boundary r=jjaschke,dom-core"
This reverts commit 793c2453f1.
Download request navigate events are fired from
turn is called e.g from the activation behavior of a and area elements
in the case of a download attribute being present.
Also split nsContentUtils::TriggerLink into separate click and
mouse-over cases.
Differential Revision: https://phabricator.services.mozilla.com/D247903
Use shadow-dom aware ordering, and pick an order for disconnected elements
based on subtree root, because there's not too much useful things to do.
The spec should probably define what happens in those cases I guess...
That's not a useful order, mind you, but it prevents breaking the invariants
the sort algorithms rely on.
Change the comparison to return an int just because it's easier to debug.
Differential Revision: https://phabricator.services.mozilla.com/D237878
There are some callers of parent/offset version which computes offset before.
However, the offset may not be used. Therefore, the callers should use
`RangeBoundaryBase` version.
Additionally, if only one of the pairs is computed from `RangeBoundaryBase`,
such callers should use the `RangeBoundaryBase` version too because the offset
computation may be skipped. In this case, temporary `RangeBoundaryBase` should
be a `RawRangeBoundary` and whose `aRangeIsMutationObserver` should be set to
`RangeBoundaryIsMutationObserved::No` to avoid immediately to compute the child
node from `aOffset`. I think that this should be default to
`RangeBoundaryIsMutationObserved::No` in the future, but for now, we should just
make the users explicitly set it to `RangeBoundaryIsMutationObserved::No` for
avoiding regressions.
Differential Revision: https://phabricator.services.mozilla.com/D236793
All their users should use the newer one which does not have the out-param
for "disconnected" case and indicates that with `Nothing` of `Maybe`.
Differential Revision: https://phabricator.services.mozilla.com/D236792
The `RangeBoundaryBase` version of `nsContentUtils::ComparePoints_Deprecated()`
calls the parent/offset pair version of it with computing the offsets.
However, the offset is used only when the parent node is the closest common
ancestor. Therefore, the offset may be unnecessary in a lot of cases, but
we pay expensive cost to compute the unnecessary index.
This patch creates a utility class, `CommonAncestors` for computing common
ancestors and children of the closest common ancestor, and creates 3 methods
which compare a child node and offset or another (or same) child node without
computing index of the given child node if it's possible and reasonable.
So, in the advantageous situations, this makes the comparison faster. However,
the case is not so many according to the benchmark results.
Differential Revision: https://phabricator.services.mozilla.com/D236791
There are probably other simplifications that can be done after this on the
windows side of things, but I tried to keep this minimal.
Differential Revision: https://phabricator.services.mozilla.com/D229765
There are probably other simplifications that can be done after this on the
windows side of things, but I tried to keep this minimal.
Differential Revision: https://phabricator.services.mozilla.com/D229765
Use LayoutDevice units for most these things, since it's what they are:
ScreenIntSize(presContext->AppUnitsToDevPixels(size.width), ...
Is clearly a lie :)
Differential Revision: https://phabricator.services.mozilla.com/D228586
Those query interfaces on image load show up in profiles, eg it's about 0.05% of total time of the NewsSite test on sp3.
Differential Revision: https://phabricator.services.mozilla.com/D192726
Those query interfaces on image load show up in profiles, eg it's about 0.05% of total time of the NewsSite test on sp3.
Differential Revision: https://phabricator.services.mozilla.com/D192726
