Bug 133975 - Change of -webkit-overflow-scrolling causes a layout regardless of whether a stacking context was removed or added
Summary: Change of -webkit-overflow-scrolling causes a layout regardless of whether a ...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Layout and Rendering (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-06-17 03:02 PDT by Nick Maynard
Modified: 2014-06-17 09:07 PDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nick Maynard 2014-06-17 03:02:19 PDT
This bug: 
https://bugs.webkit.org/show_bug.cgi?id=120535

Adds a changeset to ensure that a layout is performed when the value of -webkit-overflow-scrolling changes, down to the creation/destruction of a stacking context.

In situations where the element has a stacking context for another reason (-webkit-transform, for example), there will already be a stacking context on the element.  Consequently, a change to -webkit-overflow-scrolling will have no effect on the existence of a stacking context.

In these cases, we see a visible flicker when the (unnecessary) layout is performed.

Perhaps a check to see if a layout is required based on the consequent creation/destruction of a stacking context would be more appropriate.
Comment 1 Simon Fraser (smfr) 2014-06-17 09:07:54 PDT
(In reply to comment #0)
> In these cases, we see a visible flicker when the (unnecessary) layout is performed.

A layout which results in the same rendering should not cause a flicker.  What OS are you reporting this flicker on?