@dragonsqrrl
"unnecessary SVG font requirements that have nothing to do with properly rendering modern web pages."
- SVG font are a standard. Them should give support.
"This is why FF has been stuck at 97% for what seems like forever. It would've been a pointless waste of time to implement a small subset of the SVG spec
> limi.net/articles/firefox-acid3/"
- The fox and the grapes. Good job Fire"fox".
"just to pass Acid 3, which is basically the only reason to do it"
- Them must give support not to pass a test, but to support a standard.
Of course, ignore the fact that SVf font are a standard and Firefox wants to sell as the "defender of the standards" and that "always supports" them (only when it suits him).
"(but Opera developers seems to think otherwise)."
- Opera developers seems to think that SVG font are a stantdard, then is implement.
"The creators of the Acid test recognized this issue and, among other revisions, removed these SVG font requirements, although it took them a while to do so."
- The creators of the Acid test recognized the issue "Firefox should pass the test" then should get off a standard (font SVG), but instead let specifications that are not yet a standard (for example text-shadow).
"Acid 3 is a specification now?... lol, that's news to me"
- Acid 3 no, but SVG font yes.
@phate "They removed useless kruft that was nolonger part of web standards."
- Error. SVG font ARE standard. But, for example, text-shadow not yet standard, and are not removed.