Closed Bug 303059 Opened 19 years ago Closed 19 years ago

After clicking a link with tooltip, the tooltip won't go away

Categories

(Core :: DOM: Core & HTML, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 303267

People

(Reporter: ria.klaassen, Assigned: bryner)

References

()

Details

(Keywords: regression)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050801 Firefox/1.0+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050801 Firefox/1.0+

This is not my link, but I happened to see it visiting Bug 302982.
As this is a quite other issue, I thought it was better to file a separate bug
for it instead commenting in the bug.
The tooltip stays after clicking a link.
Regressed between ID:2005073013 and ID:2005073111.

Reproducible: Always

Steps to Reproduce:
1. Go to http://www.sportsline.com/mlb
2. Click on a link under Headlines
3. Click Back

Actual Results:  
The tooltip is still there, and I can't make it go away.

Expected Results:  
Tooltip should disappear at least when I hover or click in the page.
Keywords: regression
WFM, with 20050801 trunk build. The dhtml tooltip immediately disappears when I
enter the content area.
Tried it again; fails in the latest ID:2005080207 build.
Only if I set browser.sessionhistory.max_viewers to 0, the tooltips disappear
like they should.
With bfcache on, I see only the first tooltip.
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b4) Gecko/20050802 Firefox/1.0+
ID:2005080214

I'm seeing this too. Definitely related to bfcache.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: blocking1.8b4?
->bryner
Assignee: general → bryner
Flags: blocking1.8b4? → blocking1.8b4+
I think this is the same as bug 303267 (lots of errors in the js console about
undefined variables, etc).

*** This bug has been marked as a duplicate of 303267 ***
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
Flags: blocking1.8b4+
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.