For different browsers running on the same machine, some given content might perform poorly or well, depending on how features are implemented. In (1) we might want to reduce quality/correctness to make the experience better for the user. If the user finds that content doesn’t work performantly in Firefox, we might want to trade off quality/ correctness so that they don’t want to switch to another browser where certain Web features are more performant. (Alternatively we might just want to concentrate on closing the performance gap in that case. :-))
For TenFourFox, I've often toyed with implementing switches for box-shadow, blur, etc., so that people on the very low end of the spec (we still support G3 Macintoshes) can turn these rather expensive features off. I'd rather do that in a web-standard way than a one-off local change, though.
Since none of our supported systems are WebGL-capable, I'm mostly interested in graceful degradation of expensive CSS, such as reducing animation smoothness or interpolation, or browser-generated effects like blur etc.
However, I personally doubt that a web author will implement this, reasoning that it should be at the taste of the user. Maybe suggestions for an automated means would be nice, but a determined user will want to strip things out in just the way they would like, and I think they should have the opportunity to do so. There's nothing that says this has to be one or the other.
Cameron Kaiser _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
