Changes

Jump to: navigation, search

Platform/Layout/CSS Compatibility

214 bytes added, 19:51, 14 February 2012
questions and methodology: added more details, including suggestion from dbaron
== questions and methodology ==
* What are the thresholds (even approximate) for supporting an other-vendor prefixed property vs. not?
** Is there an approximate % of top N sites that justifies it?
** Is there a set of specific top sites that justifies it?
* How should we consider occurrence counts of -webkit- properties?
** Weighted by PageRank or equivalent?
* Severity of feature absence. Missing some properties breaks a lot more than missing others. Consider usability of page with/without the feature, not just how often it is used. E.g. tap-highlight-color does not affect the user's ability to use a website the same way text-size-adjust does.
== parsing other vendor prefixes approaches ==
Canmove, confirm
2,672
edits

Navigation menu