Closed Bug 304288 Opened 19 years ago Closed 19 years ago

bfcache: no mouse events on framed sites after onmousedown="history.back()" (button==0)

Categories

(Core :: DOM: Events, defect)

x86
All
defect
Not set
major

Tracking

()

RESOLVED FIXED
mozilla1.8beta4

People

(Reporter: bugs, Assigned: bryner)

References

()

Details

(Keywords: fixed1.8, regression)

Attachments

(1 file)

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

Make sure that bfcache (browser.sessionhistory.max_viewers > 0) is enabled.
Make sure that JavaScript is enabled.

Tested on WinXP and Fedora Core3.

Reproducible: Always

Steps to Reproduce:
1.load http://www.krickelkrackel.de/index2.htm
2.leftclick "Info"
3.leftclick "HOME"
4.left-mouse-down on Zappa's face. ("history.back()" is called)
5.try to click on any link (left or middle click)
6.nothing happens. Hover not recognized.
7.only "oncontextmenu" is recognized

Actual Results:  
Some mouse actions not working.

Expected Results:  
Perform mouse actions.
With bfcache disabled, this WFM. When enabled, I see the bug... Marking as a
blocker for bug 274784 and nominating for 1.8b4 - this is pretty nasty. CCing
Bryner.
Severity: normal → major
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: blocking1.8b4?
Keywords: regression
Chase, brendan says this might be a bug you were showing him at tinderbox. Does
that sound right? 

BZ, can you help us look into this?
I have encountered something that looked suspiciously like this on numerous
occasions.
Tested with both:
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050810
SeaMonkey/1.0a
and
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050811
SeaMonkey/1.0a

My father noticed the bug when I stuck the latest SeaMonkey build on his system
last night.

Assuming it's the same bug, it's not limited to framed sites.

Steps to reproduce on WinXP:

1. Load: http://www.mi-mls.com:81/brtest/brsearch.php3

2. Navigate away from the page
This can include any of the following:
A. go back to the previous page in the history
B. click on any of the links to proceed to a new page
C. navigate to any other address

3. Return to the page (using back/forward)
4. Try to click on any of the buttons

After initially loading (or after reloading) the page, the buttons will work as
is expected.

As the previous comments have indicated, the bug shows up when bfcache is
enabled, but not when disabled.
I submitted comment 23 to bug 295931.  As mentioned by Jochen in that bug I
believe that my comment belongs to this bug instead.  Reproduced here:

I have bfcache enabled and I consistently see a similar problem.  It seems to
happen most (only?) on sites with frames.

To reproduce:
a) Visit a site with frames, such as http://www.eclipse.org
b) Click a link within a frame
c) Use rocker navigation to go back a page

The result is that I'm no longer able to select text, click on links, or any
other interaction with the page (including further rocker navigation).  Note
that this affects the entire page, not just the frame I went back/forward on. 
It is not fixed by the Ctrl+N suggestion mentioned above, nor by
minimze/restore.  Reloading the page does fix it, however.

Extension I have installed include IEView 1.2.4, DOM Inspector 1.7+, Reporter
1.7+ and Mouse Gestures 1.0.  I'm running the most recent Deer Park nightly.
Bryner - looks to be bfcache related.  Can you take a look?

Assignee: events → bryner
Flags: blocking1.8b4? → blocking1.8b4+
another URL for the testcase, since some people are getting 404:
http://steelgryphon.com/testcases/nomouse.htm
Target Milestone: --- → mozilla1.8beta4
The problem seems to be that the mouse stays grabbed by the old document's 
view.  Fix coming up.
Attached patch patchSplinter Review
Release any mouse grabs that point into the view hierarchy being removed.
Attachment #193094 - Flags: review?(roc)
Attachment #193094 - Flags: approval1.8b4?
Flags: blocking1.8b5+
Comment on attachment 193094 [details] [diff] [review]
patch

Please get this in the trunk and if it looks good land on the branch.
Attachment #193094 - Flags: approval1.8b4? → approval1.8b4+
landed on trunk (yesterday), and branch (today)
Status: NEW → RESOLVED
Closed: 19 years ago
Keywords: fixed1.8
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: