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

From MozillaWiki
< QA‎ | Firefox3.1
Jump to navigation Jump to search
Line 40: Line 40:


* Embedded OpenType fonts are not displayed (at least on Mac)
* 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 [[https://bugzilla.mozilla.org/show_bug.cgi?id=441473#c33| bug 441473 #33]]
* The layout after the new fonts load seems to be based on the old layout, as is mentioned in [https://bugzilla.mozilla.org/show_bug.cgi?id=441473#c33 bug 441473 #33]
* Firefox crashes when you leave the page before the font download finishes.
* Firefox crashes when you leave the page before the font download finishes.
** For example, this test page [[http://people.mozilla.org/~ctalbert/fontface/downloadable-font-crashtest.html http://people.mozilla.org/~ctalbert/fontface/downloadable-font-crashtest.html]] should crash your firefox (only if have applied the patch for bug 441473).
** For example, the following test page should crash your firefox (only if have applied the patch for bug 441473).
** [http://people.mozilla.org/~ctalbert/fontface/downloadable-font-crashtest.html http://people.mozilla.org/~ctalbert/fontface/downloadable-font-crashtest.html]
* Unknown gryph change happens to some Japanese characters when font (which does not contain Japanese characters) is downloaded and rendered.
* 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.
** I think it shouldn't change.
** Now filed as [https://bugzilla.mozilla.org/show_bug.cgi?id=451426 bug 451426]
** It only happens when the file is encoded in Japanese encoding (Shift_JIS, EUC-jp). It doesn't happen if the file is encoded in UTF-8.
** It only happens when the file is encoded in Japanese encoding (Shift_JIS, EUC-jp). It doesn't happen if the file is encoded in UTF-8.
* 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?

Revision as of 22:52, 20 August 2008

« QA/Firefox3.1/FontFace TestPlan

Notes

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

Executed Tests

(Tests Already Executed)

  • Pair-wise 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
  • Tests to make sure downloaded fonts cannot be used from other documents

Planned (but not executed) Tests

(Tests Not Executed Yet)

See the TestPlan for details.

Possible Risks

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

  • 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
  • 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 only happens when the file is encoded in Japanese encoding (Shift_JIS, EUC-jp). It doesn't happen if the file is encoded in UTF-8.
  • 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.
  • How about Datafork TrueType fonts? How about bitmap fonts?