This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 12297 - Please specify how to handle space, tab and carriage return in title attribute values
Summary: Please specify how to handle space, tab and carriage return in title attribut...
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
Depends on:
Reported: 2011-03-14 09:43 UTC by Henri Sivonen
Modified: 2011-08-04 05:16 UTC (History)
7 users (show)

See Also:


Description Henri Sivonen 2011-03-14 09:43:24 UTC

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!)
Comment 1 Henri Sivonen 2011-03-14 09:44:00 UTC
Since IE is older, we should probably go with the tab size of 8.
Comment 2 Anne 2011-03-14 10:06:47 UTC
8 is also the default CSS uses (some browsers allow adjusting it) so that would make sense.
Comment 3 Anne 2011-03-14 10:08:28 UTC
See second point of the second list in
Comment 4 Ian 'Hixie' Hickson 2011-05-07 20:39:17 UTC
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:

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.
Comment 5 contributor 2011-05-07 20:39:32 UTC
Checked in as WHATWG revision r6121.
Check-in comment: Recommend that TAB be supported in tooltips.
Comment 6 Henri Sivonen 2011-05-09 09:36:16 UTC
Comment 7 Michael[tm] Smith 2011-08-04 05:16:04 UTC
mass-move component to LC1