Closed
Bug 229237
Opened 21 years ago
Closed 21 years ago
Image "title" attribute text does not display whitespace properly in tooltips
Categories
(SeaMonkey :: General, defect)
SeaMonkey
General
Tracking
(Not tracked)
People
(Reporter: jtalkington, Assigned: aaronlev)
References
()
Details
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7a) Gecko/20031220 Firebird/0.7+
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7a) Gecko/20031220 Firebird/0.7+
HTML doesn't really define what to do with whitespace in the "title" attribute
of elements, but XHTML states clearly that leading and trailing whitespace
should be stripped and sequences of multiple whitespace characters (including
line breaks,) should be mapped to a single inter-word space.
Reproducible: Always
Steps to Reproduce:
1. Visit a page that has line breaks in image titles (http://tinyurl.com/ytf3g)
Actual Results:
Funky characters appeared in the tooltip, and the leading/trailing whitespace is
left intact.
Expected Results:
The leading/trailing whitespace should be stripped and multiple whitespace
characters/line breaks should be mapped to a single inter-word space.
Reporter | ||
Updated•21 years ago
|
Component: Accessibility APIs → Browser-General
Mozilla v1.4 and v1.5 (Windows XP and Red Hat Linux 7.1) show this symbol.
Netscape Communicator v4.8 and Internet Explorer v6.0 SP1 (all updates) don't
show this problem. I know IE will break without that symbol.
I have an example as well: http://home.apu.edu/~philpi/temp/title-mozilla.html
and shared my finds with others before adding comments to this bug #.
Comment 2•21 years ago
|
||
That's because CRLF aren't valid here (see bug 47078 comment 16), although many
people want to use them to have multi-line tooltips (bug 67127) or they want
them to be stripped (bug 47078).
*** This bug has been marked as a duplicate of 47078 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•