QA/Firefox3.1/FontFace TestStatus: Difference between revisions

From MozillaWiki
< QA‎ | Firefox3.1
Jump to navigation Jump to search
Line 51: Line 51:
== Tests on Windows XP SP3 ==
== Tests on Windows XP SP3 ==


10% of Combination Tests
5% of Combination Tests


= Planned (but not executed) Tests =
= Planned (but not executed) Tests =

Revision as of 23:02, 22 August 2008

« 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 Possible Risks section for details.

Tests on Mac OS X

Combination Tests for the following features:

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 (*)

Tests on Windows XP SP3

5% of Combination Tests

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).
  • The layout after the new fonts load seems to be based on the old layout, as is mentioned in bug 441473 #33
  • Fallback function not working on Mac OS X
    • 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.

Suspected features (are these bug? or expected behaviors?)* 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
  • Font-weight, font-style and font-stretch descriptors seems to be ignored
    • It seems that only data in the font itself is used to determine the characteristics of downloadable fonts
    • Font-stretch property itself is not implemented yet
  • Some fonts are not rendered on Windows
    • It doesn't have relationship with font formats like TrueType or OpenType. Some OpenType fonts are drawn correctly, and some are not drawn.
    • When it fails, message like the following is displayed on the console:

Expected Features

  • Embedded OpenType fonts are not displayed (at least on Mac)
  • Does not support Datafork TrueType fonts
  • Does not support bitmap fonts?
Retrieved from "https://wiki.allizom.org/index.php?title=QA/Firefox3.1/FontFace_TestStatus&oldid=105439"