| Summary: | [iOS] Do not flatten frames when async frame scrolling is enabled | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Frédéric Wang (:fredw) <fred.wang> | ||||||
| Component: | Frames | Assignee: | Frédéric Wang (:fredw) <fred.wang> | ||||||
| Status: | RESOLVED FIXED | ||||||||
| Severity: | Normal | CC: | fred.wang, simon.fraser, webkit-bug-importer | ||||||
| Priority: | P2 | Keywords: | InRadar | ||||||
| Version: | WebKit Nightly Build | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Bug Depends on: | 171914 | ||||||||
| Bug Blocks: | 149264, 183081 | ||||||||
| Attachments: |
|
||||||||
|
Description
Frédéric Wang (:fredw)
2017-06-22 02:30:50 PDT
Created attachment 313604 [details]
Patch
The patch is bit-rotten. It seems that the new iOS simulator exposes experimental features which make this more interesting now. Maybe we can just completely disable frame flattening instead of just enabling the heuristics? Created attachment 321946 [details]
Patch
Comment on attachment 321946 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=321946&action=review > Source/WebCore/page/Settings.cpp:427 > +FrameFlattening Settings::actualFrameFlattening() This is a very confusing name. Maybe "effectiveFrameFlattening" would be slightly less confusing? (In reply to Simon Fraser (smfr) from comment #4) > This is a very confusing name. Maybe "effectiveFrameFlattening" would be > slightly less confusing? OK, I'll change it. Committed r223169: <http://trac.webkit.org/changeset/223169> |