12297 2011-03-14 09:43:24 +0000 Please specify how to handle space, tab and carriage return in title attribute values 2011-08-04 05:16:04 +0000 1 1 1 Unclassified HTML WG LC1 HTML5 spec unspecified PC Linux CLOSED FIXED P2 normal --- 1 hsivonen ian annevk ayg ian jonas mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 46663 0 hsivonen 2011-03-14 09:43:24 +0000 http://www.whatwg.org/specs/web-apps/current-work/#the-title-attribute-0 For consistency with IE and Chrome, please say that CRLF, CR and LF each render one line break. Please say that runs of spaces are *not* collapsed. Please say that tabs move the next character to the next tab stop but at least by one space. Unfortunately, it seems the browsers don't agree on the tab size. Chrome has the tab size of 4. IE has the tab size of 8. (Firefox would have the tab size of 3 if you could observe it!) 46664 1 hsivonen 2011-03-14 09:44:00 +0000 Since IE is older, we should probably go with the tab size of 8. 46666 2 annevk 2011-03-14 10:06:47 +0000 8 is also the default CSS uses (some browsers allow adjusting it) so that would make sense. 46667 3 annevk 2011-03-14 10:08:28 +0000 See second point of the second list in http://www.w3.org/TR/CSS21/text.html#white-space-model 48300 4 ian 2011-05-07 20:39:17 +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: Partially Accepted Change Description: see diff given below Rationale: Added tab support. Adding CR/CRLF support seems weird; this isn't a text format, and we don't do special processing for CR anywhere else. Isn't the CR processing in the HTML parser sufficient for this? If it's a real compat need then sure, but unless there's a real compat need IMHO we shouldn't special-case CR here. 48301 5 contributor 2011-05-07 20:39:32 +0000 Checked in as WHATWG revision r6121. Check-in comment: Recommend that TAB be supported in tooltips. http://html5.org/tools/web-apps-tracker?from=6120&to=6121 48353 6 hsivonen 2011-05-09 09:36:16 +0000 Thanks. 53657 7 mike 2011-08-04 05:16:04 +0000 mass-move component to LC1