[Webkit-unassigned] [Bug 238184] New: AccessibilityRenderObject::nextSibling should allow parent differences in the presence of display: contents
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Mon Mar 21 21:15:56 PDT 2022
https://bugs.webkit.org/show_bug.cgi?id=238184
Bug ID: 238184
Summary: AccessibilityRenderObject::nextSibling should allow
parent differences in the presence of display:
contents
Product: WebKit
Version: WebKit Nightly Build
Hardware: Unspecified
OS: Unspecified
Status: NEW
Severity: Normal
Priority: P2
Component: Accessibility
Assignee: webkit-unassigned at lists.webkit.org
Reporter: tyler_w at apple.com
CC: andresg_22 at apple.com,
webkit-bug-importer at group.apple.com
AccessibilityRenderObject::nextSibling currently has this logic to return nullptr if the computed sibling has a parent different from `this`:
// Make sure next sibling has the same parent.
auto* nextObject = objectCache->getOrCreate(nextSibling);
if (nextObject && nextObject->parentObject() != this->parentObject())
return nullptr;
This is problematic in the presence of display: contents since we expect parent object differences due to the way this property affects the render tree.
Concretely, this breaks the firstChild(), nextSibling() iteration we do throughout WebKit, as when we get to an element with display: contents we get a parent mismatch and iteration stops unnecessarily.
--
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20220322/e5d5a4c0/attachment-0001.htm>
More information about the webkit-unassigned
mailing list