[Webkit-unassigned] [Bug 38220] [chromium] Add API for querying whether a WebWidget is using GPU accelerated compositing

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Fri Apr 30 18:53:11 PDT 2010


https://bugs.webkit.org/show_bug.cgi?id=38220





--- Comment #8 from Vangelis Kokkevis <vangelis at chromium.org>  2010-04-30 18:53:10 PST ---
(In reply to comment #7)
> (In reply to comment #6)
> I was just thinking in terms of whether or not accelerated compositing is
> enabled for the page.  In which case, asking the question "is accelerated
> compositing enabled?" seems natural to me.  I don't see "enable" as something
> necessarily connected to the user.  It seems like "use" could equally imply per
> request of the user.

You are right. "use" has the same issues.

> 
> Are there any examples in WebKit API or WebCore that match the semantic
> distinction you are going for?  It'd be nice to copy some convention.

I couldn't find any but what I did find, is WebCore's Settings class defined 
in WebCore/page/Settings.h, acceleratedCompositingEnabled() and
setAcceleratedCompositingEnabled() are both defined to mean whether the
accelerated compositing feature is allowed or not.  I think it would be
confusing if we were to use the exact same name with a different meaning. 

A couple of other possible options:
* isAcceleratedCompositingActive()
* isDoingAcceleratedCompositing()

-- 
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