This repository was archived by the owner on Jul 1, 2024. It is now read-only.
will-change: update browser support#330
Merged
pepelsbey merged 1 commit intooperasoftware:masterfrom Aug 17, 2015
Merged
Conversation
Contributor
Author
|
cc @aerotwist for the FYI |
|
Handy. Thanks! |
Contributor
|
@paulirish, thank you! Merging and deploying now. |
pepelsbey
pushed a commit
that referenced
this pull request
Aug 17, 2015
will-change: update browser support
For anyone else who gets linked here from MDN, here seems to be the 2022 status of this:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
webkit started implementing, so time for a refresher. (i'll go update MDN too)
Also, unrelated… but I wanted to tell someone.. here's Chrome's behavior for custom-ident's…
will-change values that trigger a compositing layer in Chrome:
source:
ComputedStyle::hasWillChangeCompositingHint()will-change values that trigger a stacking context in chrome
source:
hasWillChangeThatCreatesStackingContextalso
scroll-positiondoes nothing in Chrome currently.contentsappears to be a compositing layer hint for whatever children are being changed.