70
edits
Stuartmorgan (talk | contribs) (Clarify the name) |
Stuartmorgan (talk | contribs) (case fix) |
||
(One intermediate revision by the same user not shown) | |||
Line 1: | Line 1: | ||
= Status = | = Status = | ||
Accepted, ready for implementation. | |||
= Contributors = | = Contributors = | ||
* Last modified: July | * Last modified: July 22, 2011 | ||
* Authors: Stuart Morgan (Google) | * Authors: Stuart Morgan (Google) | ||
* Contributors: Kevin Decker (Apple) | * Contributors: Kevin Decker (Apple) | ||
Line 21: | Line 21: | ||
= Current Proposal = | = Current Proposal = | ||
WebKit already has an informal solution to this problem, defining a variable that plug-ins can query to determine compositing support using NPN_GetValue. The proposal is to formalize this as | WebKit already has an informal solution to this problem, defining a variable that plug-ins can query to determine compositing support using NPN_GetValue. The proposal is to formalize this as NPNVsupportsCompositingCoreAnimationPluginsBool, using the same value for compatibility with existing browser and plug-in implementations: | ||
NPNVsupportsCompositingCoreAnimationPluginsBool 74656 | |||
Any browser implementing compositing for the Core Animation drawing models would return true for this variable in NPN_GetValue. Browsers that returned false would be known not to support it, while browsers returning an error would need to be checked by user agent (for compatibility with browsers that support compositing but have not implemented this new specification). | Any browser implementing compositing for the Core Animation drawing models would return true for this variable in NPN_GetValue. Browsers that returned false would be known not to support it, while browsers returning an error would need to be checked by user agent (for compatibility with browsers that support compositing but have not implemented this new specification). |
edits