Bug 203112
| Summary: | A combination of scrolling and a content change can leave a fixed layer in the wrong place | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Simon Fraser (smfr) <simon.fraser> |
| Component: | Scrolling | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | ||
| Priority: | P2 | ||
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Simon Fraser (smfr)
The patch in bug 196612 changes scrollingcoordinator/ios/ui-scroll-fixed.html to avoid this bug, but we should fix the underlying bug too.
The bug is that a UI scroll can cause an offset to be applied to a CALayer in the UI process, but the combination of a content change and the scroll means that the GraphicsLayerCA ends up with the same position it had before. When that layer+scrolling tree is committed, nothing fixes up the CALayer position in the UI process.
We can also leave a wrong "approximate position" on the GraphicsLayer in this situation.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |