Closed Bug 52759 Opened 25 years ago Closed 25 years ago

Tooltip does not render <cr><lf> characters correctly

Categories

(SeaMonkey :: UI Design, defect, P3)

defect

Tracking

(Not tracked)

RESOLVED INVALID
Future

People

(Reporter: astrosmash, Assigned: bugs)

References

()

Details

Build ID: 2000091408 OS: Linux and Win32 The following usage of the 'title' tag is used at http://exn.ca: <HTML><BODY> Hello <a href=http://foo.org TITLE="This title contains multiple lines of text">There</a> The desired tooltip generated from the 'TITLE' tag should contain multiple lines of text, however, mozilla renders the tooltip as follows: 'This title||contains||multiple lines||of text' Unfortunatly, IE$ is currently the only browser that will display the tooltip in the intended manner.
Assignee: trudelle → pinkerton
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Linux → All
Hardware: PC → All
Target Milestone: --- → Future
-> pinkerton, Future
I think this bug is invalid. In HTML linebreak characters are just whitespace.
Sure Henri, but if line breaks has to be ignored for standard consistency, the Mozilla should wrap long tooltips. Look for example at http://www.w3c.org , their side table descriptions easily goes out of my monitor. I think Mozilla should wrap long tooltips to a reasonable lenght (in *max* two lines and a maximum width). A reasonable width sould be taken from the OS screen preferences. Since -I can easily imagine- would be painfull to implement in every platform, I think a reasonable solution should be set the max width of tooltips == current window width.
It would be a cool feature if we could wrap them, like the afore mentioned "long tooltips" problem.
--> xpapps
Assignee: pinkerton → ben
Component: XP Toolkit/Widgets → XP Apps
actually, invalid. if you want linebreaks, use <BR>
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → INVALID
*** Bug 83268 has been marked as a duplicate of this bug. ***
Product: Core → Mozilla Application Suite
*** Bug 273854 has been marked as a duplicate of this bug. ***
You need to log in before you can comment on or make changes to this bug.