RESOLVED FIXED 52119
CSS 2.1 failure: font-size-* (because of Safari-imposed min font sizes)
https://bugs.webkit.org/show_bug.cgi?id=52119
Summary CSS 2.1 failure: font-size-* (because of Safari-imposed min font sizes)
Simon Fraser (smfr)
Reported 2011-01-08 19:26:20 PST
The following CSS 2.1 test suite files fail: html4/font-size-001 html4/font-size-002 html4/font-size-004 html4/font-size-005 html4/font-size-012 html4/font-size-013 html4/font-size-015 html4/font-size-016 html4/font-size-023 html4/font-size-024 html4/font-size-026 html4/font-size-027 html4/font-size-034 html4/font-size-035 html4/font-size-037 html4/font-size-038 html4/font-size-045 html4/font-size-046 html4/font-size-048 html4/font-size-049 html4/font-size-056 html4/font-size-057 html4/font-size-059 html4/font-size-060 html4/font-size-067 html4/font-size-068 html4/font-size-070 html4/font-size-071 html4/font-size-078 html4/font-size-079 html4/font-size-081 html4/font-size-082 html4/font-size-089 html4/font-size-090 html4/font-size-092 html4/font-size-093 html4/font-size-100 html4/font-size-101 html4/font-size-102 html4/font-size-113
Attachments
Simon Fraser (smfr)
Comment 1 2011-01-08 19:40:45 PST
Some of these fail if you have the "minimum font size" pref enabled (which I did when testing). Even when that's off, settings->minimumFontSize() returns '1', so the tests that test a zero font size still fail.
Simon Fraser (smfr)
Comment 2 2011-01-08 19:47:12 PST
In Safari, settings->minimumLogicalFontSize() returns 9, which also breaks some tests.
Simon Fraser (smfr)
Comment 3 2011-01-08 20:09:07 PST
The only test that fails after removing the Safari-imposed min font and logical font sizes is font-size-113, which fails because of 'ex' issues (see bug 47157).
Dave Hyatt
Comment 4 2011-01-12 13:51:09 PST
Any tests that fail because of the logical font size minimum of 9 we should challenge as invalid.
Simon Fraser (smfr)
Comment 5 2011-01-12 13:55:32 PST
font-size: 0 was apparently fixed in early December. Not sure why I wasn't seeing that.
Dave Hyatt
Comment 6 2011-03-11 12:31:30 PST
All of these are fixed now.
Note You need to log in before you can comment on or make changes to this bug.