10926 2010-10-01 00:44:48 +0000 fillText or strokeText behavior needs to preserve readability of text when using maxWidth 2010-10-05 12:58:40 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML Canvas 2D Context (editor: Ian Hickson) unspecified PC All RESOLVED WONTFIX P2 normal --- 1 jmann ian annevk ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 40351 0 jmann 2010-10-01 00:44:48 +0000 Section 11 Text of the spec states: "5.If the maxWidth argument was specified and the hypothetical width of the inline box in the hypothetical line box is greater than maxWidth CSS pixels, then change font to have a more condensed font (if one is available or if a reasonably readable one can be synthesized by applying a horizontal scale factor to the font) or a smaller font, and return to the previous step." Currently the way the spec is defined, readability of text is difficult in the above situation. Further, the text “reasonably readable” is not very precise. Consider the following code: ctx.font = '1000px Arial'; ctx.fillText("HTML5 Canvas 2D Context", 0, 300, 450); IE and Firefox follow the spec, and the text is quite unreadable. Chrome and Safari do not implement maxWidth. Opera, however, renders the text at the font size that will fit in the maxWidth without scaling. Opera’s implementation here seems to make most sense – as it is readable. This text should be updated like so: "5.If the maxWidth argument was specified and the hypothetical width of the inline box in the hypothetical line box is greater than maxWidth CSS pixels, then change font size to a size that will fit in the maxWidth width without scaling the font, and return to the previous step." 40395 1 annevk 2010-10-01 07:41:27 +0000 Isn't changing the font size the same as using a smaller font? 40580 2 ian 2010-10-04 23:09:06 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: no spec change Rationale: The spec currently allows either condensing or shrinking the text (or both, actually). I don't see why requiring that the text only be shrunk would be better. In fact, it seems like it would be worse -- in edge cases, it looks better just to condense the font than to shrink it. This is a quality of implementation issue.