Closed
Bug 62050
Opened 25 years ago
Closed 25 years ago
tooltips not displayed for title attributes
Categories
(SeaMonkey :: UI Design, defect, P3)
SeaMonkey
UI Design
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: jhvr, Assigned: jag+mozbugs)
References
()
Details
(Keywords: helpwanted, regression)
Attachments
(3 files)
|
42.36 KB,
image/gif
|
Details | |
|
30.70 KB,
image/gif
|
Details | |
|
816 bytes,
patch
|
Details | Diff | Splinter Review |
As I just discovered the Title text is no longer displayed. This must be an
regression. As it worked before! And it still does in Netscape 6/6.0.
Link, images you name it, they no longer display the title informatie. So for
now, we no longer have ALT and Title information in SM, this is to odd for
words! I feel sorry for that.
Friendly, HJ
Oeps, forgot something, tested with build 2000120504 on WinNT4 Sp6
I'm only human.
Comment 2•25 years ago
|
||
I see this on 2000-12-05-08 on linux. OS->All. I would confirm but I am not
sure what the component should be for this. Other tooltips seem to work
fine.... This is definitely a regression from this past weekend -- the 11-30-08
build worked just fine.
Summary: Title text not displayed → tooltips not displayed for alt and title attributes
Comment 3•25 years ago
|
||
...and also Win2K 1205 and OS/2 "1201" (1130).
I'll attach some pictures as well.
Comment 4•25 years ago
|
||
Comment 5•25 years ago
|
||
Comment 6•25 years ago
|
||
Confirming on Linux build 2000120508, OS->All. Changing summary to remove the
"alt" attribute since the spec says that alt is for inline use. Moving Component
to XPApps on advice from Asa.
This regressed I *think* over the weekend, can't be precise. Only regressed in
web browser on html pages, not in general product.
Status: UNCONFIRMED → NEW
Component: Browser-General → XP Apps
Ever confirmed: true
Keywords: verifyme
OS: Windows NT → All
Summary: tooltips not displayed for alt and title attributes → tooltips not displayed for title attributes
Comment 7•25 years ago
|
||
this regressed between the 120208 and 120306 builds.
Comment 8•25 years ago
|
||
reassign to default component owner. I've narrowed this down further. This
regressed after the 1120206 and before the 122021 build
Assignee: asa → don
QA Contact: doronr → sairuh
Comment 9•25 years ago
|
||
looks like jag, blake and dbaron were the ones checking in in that time frame.
Can you all take a look at your checkins and see if maybe one of them regressed
this. Thanks
Assignee: don → disttsc
I'd say jag is most likely, since he cleaned up large parts of navigator.js,
although there's a small chance it could have been my navigator.js or
nsGlobalWindow changes.
jag, could you have a look? Assigning to jag... :-)
| Assignee | ||
Comment 11•25 years ago
|
||
Hrm... My mistake...
Fix is easy:
- if (tipElement.nodeType == Node.ELEMENT_NODE) {
+ if (tipElement.nodeType == 1) {
I'll attach a real patch when I'm in Linux.
Updated•25 years ago
|
QA Contact: sairuh → tpreston
| Assignee | ||
Comment 12•25 years ago
|
||
Comment 13•25 years ago
|
||
a=ben@netscape.com, per discussions on IRC. (const Node = { .. })
Comment 14•25 years ago
|
||
r=blake on the patch discussed on IRC, and 20 whippings for jag.
| Reporter | ||
Comment 15•25 years ago
|
||
Hm, it seems this is going to work out right. Thanks guy.
And please jump into line 91, getting this error day by day!
| Assignee | ||
Updated•25 years ago
|
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
| Assignee | ||
Comment 16•25 years ago
|
||
This should be fixed now.
HJ, can you file a new bug on that "error on line 91"?
| Reporter | ||
Comment 17•25 years ago
|
||
Peter, please take a look at 61029 first will you?
Friendly, HJ
Comment 18•25 years ago
|
||
*** Bug 62262 has been marked as a duplicate of this bug. ***
Comment 19•25 years ago
|
||
*** Bug 62252 has been marked as a duplicate of this bug. ***
Comment 20•25 years ago
|
||
Assigning dependency, changing Plat/OS to ALL, VERIFIED on Mac OS 2001-01-04-08.
Updated•21 years ago
|
Product: Core → Mozilla Application Suite
You need to log in
before you can comment on or make changes to this bug.
Description
•