canmove, Confirmed users
2,854
edits
Platform/Layout/CSS Compatibility: Difference between revisions
Jump to navigation
Jump to search
Platform/Layout/CSS Compatibility (view source)
Revision as of 20:17, 14 February 2012
, 14 February 2012→questions and methodology: for sites in general vs. specific sites
(→problematic sites: noted AaronMT's comparison page, and specific request for sites) |
(→questions and methodology: for sites in general vs. specific sites) |
||
| Line 32: | Line 32: | ||
== questions and methodology == | == questions and methodology == | ||
For sites in general: | |||
* What are the thresholds (even approximate) for supporting an other-vendor prefixed property vs. not? | * What are the thresholds (even approximate) for supporting an other-vendor prefixed property vs. not? | ||
* How much of this is due to user-agent sniffing? | * How much of this is due to user-agent sniffing? | ||
| Line 40: | Line 41: | ||
** Weighted by PageRank or equivalent? | ** 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. | * 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. | ||
* ... | |||
For specific sites: | |||
* *Which* sites will work *how much* better if we implement *which* properties? | |||
** The sites which are currently "broken" should be listed above in "problematic sites" and have a bug# for each one. | |||
* ... | * ... | ||