Project: chromium Issues People Development process History Sign in
New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.
Starred by 11 users
Status: Fixed
Owner:
Closed: Apr 2014
Cc:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Launch-OWP
Launch-Accessibility: ----
Launch-Legal: ----
Launch-M-Approved: ----
Launch-M-Target: ----
Launch-Privacy: ----
Launch-Security: ----
Launch-Status: ----
Launch-Test: ----
Launch-UI: ----
Product-Review: ----

Blocked on:
issue 313532



Sign in to add a comment
CSS will-change
Project Member Reported by ajuma@chromium.org, Mar 25 2014 Back to list
(See http://www.chromium.org/blink#launch-process for an overview)

Change description:
This adds a will-change CSS property, that can be used to signal that a particular property is likely to be changed in the future, or that an element’s content is likely to change.

Changes to API surface:
* new CSS property: will-change

Links:
Public standards discussion: http://lists.w3.org/Archives/Public/www-style/2013Nov/0414.html, http://lists.w3.org/Archives/Public/www-style/2014Jan/0117.html

Spec: http://tabatkins.github.io/specs/css-will-change/

Support in other browsers:
Firefox: Implemented behind a flag. https://bugzilla.mozilla.org/show_bug.cgi?id=961871 tracks enabling will-change.
 
Comment 1 Deleted
Comment 2 by ajuma@chromium.org, Mar 25 2014
Cc: tabatkins@chromium.org
Summary: CSS will-change (was: CSS wil-change)
Wahoo!
Status: Fixed
Marking as Fixed. 
Looks like we're all set here.  This feature looks like it'll track Chrome 36.

Link-drop for the curious: http://www.aerotwist.com/blog/bye-bye-layer-hacks/
And, for what it's worth, will-change is now a First Public Working Draft, set to proceed to LC/CR in a month or two: http://www.w3.org/TR/css-will-change/
Sign in to add a comment