1822694 - WPT css-contain/content-visibility/content-visibility-048.html fails in Firefox

Status: NEW

(Core :: Layout, defect)

Description

[Daniel Holbert [:dholbert]]

Test results:
https://wpt.fyi/results/css/css-contain/content-visibility/content-visibility-048.html

If I'm reading the test correctly, it looks like it's testing that e.g. navigating to foo.html#target can properly scroll to #target (i.e. <div id="target">) even if that element happens to be inside of an element that skips its contents.

Comment 1

[Daniel Holbert [:dholbert]]

(In reply to Daniel Holbert [:dholbert] from comment #0)

If I'm reading the test correctly, it looks like it's testing that e.g. navigating to foo.html#target can properly scroll to #target (i.e. <div id="target">) even if that element happens to be inside of an element that skips its contents.

There's more to the failure, though, because things do seem to work when I try to do that^ directly -- e.g. if I load these URLs (with content-visibility enabled)...
http://wpt.live/css/css-contain/content-visibility/resources/text-fragment-target-auto.html#text
http://wpt.live/css/css-contain/content-visibility/resources/text-fragment-target-auto.html#text2

...then I do end up seeing the referenced element, scrolled partway down the page. So there's some additional subtlety to the failure here.

Comment 2

[cathiechen]

It looks like the cases is using a fragment directive [1]: '#:~:text=hiddentext', which is not supported in Gecko yet.[2]
Maybe this wpt test should not block content-visibility?

[1] https://wicg.github.io/scroll-to-text-fragment/#the-fragment-directive
[2] https://caniuse.com/url-scroll-to-text-fragment

Comment 3

[Frédéric Wang]

Yes, so we currently have an expected failure on all platforms: https://searchfox.org/mozilla-central/rev/1a63fee6c2a8ea6846f6f16b85edeb6d19fc9f23/testing/web-platform/meta/css/css-contain/content-visibility/content-visibility-048.html.ini

This is probably bug 1753933.