Bug 235240

Summary:	Make a consistent way to compute applied opacity
Product:	WebKit	Reporter:	Simon Fraser (smfr) <simon.fraser>
Component:	Layout and Rendering	Assignee:	Nobody <webkit-unassigned>
Status:	NEW
Severity:	Normal	CC:	andresg_22, bfulgham, ntim, simon.fraser, webkit-bug-importer, zalan
Priority:	P2	Keywords:	InRadar
Version:	Safari Technology Preview
Hardware:	Unspecified
OS:	Unspecified

Simon Fraser (smfr)

Reported 2022-01-14 10:46:12 PST

Walking the renderer parent chain is wrong with top layer (dialog, ::backdrop).

Attachments
Add attachment proposed patch, testcase, etc.

Radar WebKit Bug Importer

Comment 1 2022-01-14 10:46:24 PST

<rdar://problem/87607943>

Simon Fraser (smfr)

Comment 2 2022-01-14 10:48:29 PST

HTMLPlugInElement::isReplacementObscured() and ContentChangeObserver::isVisuallyHidden() do the same thing.

Simon Fraser (smfr)

Comment 3 2022-01-14 10:53:06 PST

And RenderLayer::isTransparentRespectingParentFrames()

Simon Fraser (smfr)

Comment 4 2022-01-19 11:20:38 PST

HTMLPlugInElement::isReplacementObscured() and RenderLayer::isTransparentRespectingParentFrames() use the layer parent() chain so bug 235194 fixes them. ContentChangeObserver::isVisuallyHidden() is wrong.

Tim Nguyen (:ntim)

Comment 5 2022-01-19 12:25:40 PST

Would walking up the stacking context chain be a fix here?

Simon Fraser (smfr)

Comment 6 2022-01-19 13:02:33 PST

Walking paintOrderParent(), yes.

Tim Nguyen (:ntim)

Comment 7 2022-02-27 01:57:30 PST

AXObjectCache::isNodeVisible() was the example mentioned in the original bug title.

Note You need to log in before you can comment on or make changes to this bug.