193
edits
QA/Firefox3.1/FontFace TestStatus: Difference between revisions
QA/Firefox3.1/FontFace TestStatus (view source)
Revision as of 18:41, 21 August 2008
, 21 August 2008→Possible Risks
Ayoshihara (talk | contribs) |
Ayoshihara (talk | contribs) |
||
| Line 45: | Line 45: | ||
** I think it shouldn't change. | ** I think it shouldn't change. | ||
** Now filed as [https://bugzilla.mozilla.org/show_bug.cgi?id=451426 bug 451426] | ** Now filed as [https://bugzilla.mozilla.org/show_bug.cgi?id=451426 bug 451426] | ||
** It | ** It happens when the file is encoded in Japanese encoding (Shift_JIS, EUC-jp). | ||
* Embedded OpenType fonts are not displayed (at least on Mac) | * Embedded OpenType fonts are not displayed (at least on Mac) | ||
| Line 51: | Line 51: | ||
* When it fails to download the font from every URI written in src, it just doesn't display anything ... shouldn't it display in default font? | * When it fails to download the font from every URI written in src, it just doesn't display anything ... shouldn't it display in default font? | ||
* Also, when the url written in src did exist but was not in a proper format, it displays nothing. Even if they had other candidates after that url, those candidates are ignored. | * Also, when the url written in src did exist but was not in a proper format, it displays nothing. Even if they had other candidates after that url, those candidates are ignored. | ||
* Same-origin restriction is not implemented yet. | |||
* How about Datafork TrueType fonts? How about bitmap fonts? | * How about Datafork TrueType fonts? How about bitmap fonts? | ||