[Webkit-unassigned] [Bug 105558] New: Get rid of acceleratedCompositingForScrollableFramesEnabled altogether
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Thu Dec 20 11:45:19 PST 2012
https://bugs.webkit.org/show_bug.cgi?id=105558
Summary: Get rid of
acceleratedCompositingForScrollableFramesEnabled
altogether
Product: WebKit
Version: 528+ (Nightly build)
Platform: Unspecified
OS/Version: Unspecified
Status: NEW
Severity: Normal
Priority: P2
Component: Layout and Rendering
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: tonikitoo at webkit.org
CC: jamesr at chromium.org, vangelis at chromium.org
Depends on: 71714
Talked to James Robinson about this a couple of some months ago, and just got around this code again and remember.
Pasted below the relevant bits of conversion:
(...)
705190 Sep 21 16:27:44 <jamesr_> acceleratedCompositingForScrollableFramesEnabled could probably just go away completely
705193 Sep 21 16:28:22 <tonikitoo> jamesr_, can it? in favor of anything else?
705194 Sep 21 16:28:31 <tonikitoo> let me know, and I can help with that
705195 Sep 21 16:28:56 <jamesr_> tonikitoo, so when we initially added force compositing mode we automatically promoted iframes too (it helped with gmail at the time)
705196 Sep 21 16:29:01 <jamesr_> but then gmail rewrote their dom, heh
705197 Sep 21 16:29:22 <jamesr_> so we added this to get forceCompositingMode back to just entering compositing mode but not promoting anything
705198 Sep 21 16:29:44 <jamesr_> while still having the other behavior available. i don't think we want that other behavior at all nowadays, so we could just get rid of it
705201 Sep 21 16:30:29 <jamesr_> tonikitoo, so i think we could just drop the setting
705202 Sep 21 16:30:37 <jamesr_> at least, chromium isn't using it right now afaik
--
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the webkit-unassigned
mailing list