MozillaWiki

QA/Firefox3.1/FontFace TestStatus

< QA‎ | Firefox3.1
Revision as of 22:27, 21 August 2008 by Ayoshihara (talk | contribs) (→‎Executed Tests)

« QA/Firefox3.1/FontFace TestPlan

Notes

@font-face test status Test Plan: @font-face TestPlan

Executed Tests

(Tests Already Executed)

Tests marked with star (*) shows that some unexpected features were found. See [FontFace_TestStatus#Possible_Risks Possible Risks] section for details.

Combination Tests for the following features (on Mac OS X):

Font Face serif, sans-serif, cursive, Asian, Arabic
Font Format TrueType, OpenType, TrueType-AAT(Apple Advanced Typography), EOT(Microsoft Embedded OpenType)
Source url, local
File Encoding Western, UTF-8, Shift_JIS, and other language-specific encodings

Font name tests

  • Font with multiple names (*)
  • When family-name was overrode by @font-face rules

Font source tests

  • Fallback function tests (*)

Rules tests

  • when multiple @font-face rules was in a single file
  • when multiple font face was assigned to a single font-family by @font-face
    • font matching algorithm (font-weight, font-style, font-stretch) (*)
    • how CSS marksups and HTML tags affect (*)

Others

  • Tests to make sure downloaded fonts cannot be used from other documents
  • Printing Test
  • Same origin policy test (*)

Planned (but not executed) Tests

(Tests Not Executed Yet)

See　the TestPlan for details.

Possible Risks

(Known bugs, not-yet-implemented features, questions)

Bugs already Filed in bugzilla:

  • Firefox crashes when you leave the page before the font download finishes.
  • Unknown gryph change happens to some Japanese characters when font (which does not contain Japanese characters) is downloaded and rendered.
    • I think it shouldn't change.
    • Now filed as bug 451426
    • It happens when the file is encoded in Japanese encoding (Shift_JIS, EUC-jp).

Suspected features (are these bug? or expected behaviors?)

  • Embedded OpenType fonts are not displayed (at least on Mac)
  • The layout after the new fonts load seems to be based on the old layout, as is mentioned in bug 441473 #33
  • 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.
  • Same-origin restriction is not implemented yet.
  • Some fonts have more than two font names (ex. HiraKakuPro-W3 and ヒラギノ角ゴ Pro W3). src:local() cannot recognize font names written in Japanese
    • Normal font-family: ""; can recognize font names written in Japanese
  • MEMORY LEAK occurs when you try to download something...

Others

  • How about Datafork TrueType fonts? How about bitmap fonts?

Obstacle to check-in

  • Is it possible to install a font to user's machine?
    • When we are to test @font-face { src:local(aFontFaceName) } rules, we have to make that the specified font is installed in the user's system.
  • Would there be any problem to upload a font to a web server, regarding to the license?
    • When we are to test @font-face { src:url(aFontFaceURL) } rules, we have to upload that font file to a web server. Does that violate any license? (Would it be regarded as redistribution?)
Retrieved from "https://wiki.allizom.org/index.php?title=QA/Firefox3.1/FontFace_TestStatus&oldid=105278"