New issue
Advanced search Search tips

Issue 739909 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Jul 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Chrome , Mac
Pri: 2
Type: Bug



Sign in to add a comment

opaque scrollers not composited on low DPI?

Project Member Reported by skobes@chromium.org, Jul 6 2017

Issue description

On low-DPI Linux ToT, Chrome does not composite this scroller:

  https://output.jsbin.com/mabuno/quiet

I thought that it should after  issue 381840 .  Am I missing something or is there a regression?

If I pass --enable-prefer-compositing-to-lcd-text I get both compositing and LCD text, so at least the fix in  issue 660472  is working.  There should be no reason not to promote it by default.
 
Oh wait  issue 660472  is a slightly different thing.  I guess it's r410797 that gives me the LCD text with compositing.
We'd have to know that it doesn't have any positioned children, because if it did, they would be separately promoted as the scroller isn't a stacking context (which happened on Gmail when it was enabled). See  issue 666147 .

However, it's probably rarely okay to promote currently as many sites use position to set containing blocks for descendants. So to get most sites we'd need to detect when those positioned descendants are opaque or when they don't need to be stacked separately from the scroller.
Status: WontFix (was: Unconfirmed)
Ahh that makes sense.  I do get compositing if I make it a stacking context.  Thanks for explaining.

Sign in to add a comment