Closed Bug 62050 Opened 25 years ago Closed 25 years ago

tooltips not displayed for title attributes

Categories

(SeaMonkey :: UI Design, defect, P3)

defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: jhvr, Assigned: jag+mozbugs)

References

()

Details

(Keywords: helpwanted, regression)

Attachments

(3 files)

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.
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
...and also Win2K 1205 and OS/2 "1201" (1130). I'll attach some pictures as well.
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
this regressed between the 120208 and 120306 builds.
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
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
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... :-)
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.
QA Contact: sairuh → tpreston
a=ben@netscape.com, per discussions on IRC. (const Node = { .. })
r=blake on the patch discussed on IRC, and 20 whippings for jag.
Hm, it seems this is going to work out right. Thanks guy. And please jump into line 91, getting this error day by day!
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
This should be fixed now. HJ, can you file a new bug on that "error on line 91"?
Peter, please take a look at 61029 first will you? Friendly, HJ
*** Bug 62262 has been marked as a duplicate of this bug. ***
*** Bug 62252 has been marked as a duplicate of this bug. ***
Assigning dependency, changing Plat/OS to ALL, VERIFIED on Mac OS 2001-01-04-08.
Status: RESOLVED → VERIFIED
Depends on: 56702
Hardware: PC → All
Product: Core → Mozilla Application Suite
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: