css/css-contain/content-visibility/content-visibility-068.html is failing
Categories
(Core :: Layout, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox109 | --- | fixed |
People
(Reporter: mrobinson, Assigned: mrobinson)
References
Details
Attachments
(1 file)
This test is failing after the implementation of content-visibility: auto. The reasons seems to be related to the fact that the content-visibility: auto initially has focus when in Chrome it does not.
|
Assignee | |
Comment 1•2 years ago
|
||
The issue here seems to be in the last step. The test runs blur() on a focused offscreen element inside a content-visibility: auto element. This should cause the contents to no longer be relevant and to be hidden. This isn't happening because in Gecko, the blur() call is removing focus, but the selection is still on the parent element with content-visibility: auto. I think in this case the test could focus another element to ensure that the selection also moves entirely away from the content-visibility: auto contents and element.
|
||
Updated•2 years ago
|
|
|
Assignee | |
Comment 2•2 years ago
|
||
Fix a WPT test relating to content-visibility: auto and
content-relevancy. This test attempts to change the relevancy of content
by blurring it, but relevancy also depends on selection. Apparently,
Gecko differs from other browsers in that blur() is not moving the
selection as well. The fix is to simply focus another element which will
update both focus and the text selection.
|
||
Updated•2 years ago
|
|
||
Comment 5•2 years ago
|
||
| bugherder | ||
Description
•