128998 - tooltips layout (title="tooltip") depends on theme

Status: RESOLVED EXPIRED

(SeaMonkey :: Themes, defect)

Description

[Vlad Harchev]

The way tooltips are presented depends on the theme. If the tooltip
value contains newlines in it, with Classic theme, the tooltip will
be broken in several lines, while with Modern tooltip value will be
displayed in one line (I didn't try other themes).
 I think that ability to have multiline tooltips is great and very
useful for various things (mostly for tables with a lot of data in each
cell - the tooltip would contain detailed info for the cell, while
the cell itself will contain abbreviated info to make table tighter.
MSIE honors line newlines in tooltip value.
 My mozilla version is 0.9.6 (as shipped with RH72).
 Sample (see the tooltip with Classic and Modern theme):



<span title="line1
line2
line3">hover a mouse over this using Classic and Modern themes</span>

Comment 1

[Chu Alan #2]

um ... title attribute is a plain text so it has NO specifc formatting and user
agent can reflow the title text freely, ignoring the original formatting in
attribute.

may be adding newlines support in title="" can be an enhancement for quirk mode
... or this bug is simply invalid.

Comment 2

[Christopher Hoess (gone)]

Duplicate of bug 67127, perhaps?

Comment 3

[Boris Zbarsky [:bzbarsky]]

This has nothing to do with the DOM if it's theme-specific.

Comment 4

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 5

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420