211715 - Back button and history.back() don not work when a frame with server-push is loaded

Status: RESOLVED EXPIRED

(Core :: DOM: Navigation, defect)

Description

[Luiz Fernando B. Ribeiro]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3.1) Gecko/20030618 Debian/1.3.1-3
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3.1) Gecko/20030618 Debian/1.3.1-3

In a frameset where one of the frames is using server-push, it nevers finishes
loading, the global back button and the history.back() js call does not work for
any of the frames.

Reproducible: Always

Steps to Reproduce:

Comment 1

[Phil Schwartau]

---> History:Session

Comment 2

[MightyMu]

Reporter, do you have an example URL? A site that meets the conditions you
describe? Or, better yet, a testcase?

Comment 3

[Luiz Fernando B. Ribeiro]

Hi,

It is difficult to me to provide a test case since it requires a CGI script to
run  a server push frame, but i will try to explain better.

The page is composed of 3 frames, top, center, botton.
The top frame is a navigation page including a back button.
The center frame is a regular page.
The botton frame is kind of chat frame, a CGI script sends the following HTTP
headers:
HTTP/1.0 200 Document follows
Server: Chat Server
Content-type: text/html

and the CGI never finishes sending the page, 1 line at each minute. This is a
much better implementation than plain refreshs.

In this situation, since the the botton frame never finishes loading, the back
button does not work anymore. 

This same app works perfectly in all other browsers including IE, Konqueror and
Opera.

Please notify me if you need further information.

Comment 4

[Jerry Russell]

Using "Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.2) Gecko/20030208
Netscape/7.02" along with the Jetty Servlet container, we see this problem
occasionally. Back button does not work when a frame is loaded - it does seem
random though when it does and does not work.

I did some research into Jetty's bug db and found registered bug 699011 which is
that Jetty sends HTTP/1.1 100 CONTINUE messages unnecessarily.  Would this cause
the same issue if a final response is not sent accordingly?

Comment 5

[Boris Zbarsky [:bzbarsky]]

I could try to look into this if someone can put up a URL where I can reproduce
the problem...

Comment 6

[Steven Grimm]

http://www.ironplanet.com/j/equip/auction.jsp?groupId=206

Works fine in IE; in Mozilla the back button either doesn't work at all or
requires multiple presses.

Comment 7

[Boris Zbarsky [:bzbarsky]]

Works fine over here in a current trunk build.  Please make sure that you're
usinga build with the fix for bug 237717 in it (trunk build from April 13, 2004
or later).  Builds without that fix _do_ show the problem on
http://www.ironplanet.com/j/equip/auction.jsp?groupId=206 but builds with that
fix don't seem to.

Comment 8

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 9

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.

Comment 10

[Aamir Latif]

I have added an iframe in my page and use links to load pages in iframe. But on clicking history back button, previous page does not load in iframe in Firefox 2.0.0.12. This works fine with IE6, IE7. This bug is still persist in Firefox.

Comment 11

[Boris Zbarsky [:bzbarsky]]

Aamir Latif, can you please point to a URI actually showing your problem?

Comment 12

[Chris Harrison]

This bug has still not been resolved.

An example URL is http://ajaxim.com/ The back link is broken because the chat is using an iFrame at the bottom which seems to be refreshing in some way.

No other modern browser has this problem.

Comment 13

[Boris Zbarsky [:bzbarsky]]

Chris, which Firefox version were you testing?  If I click the link in comment 12 in a current trunk nightly and then click back, I end up on this bug page.

Comment 14

[Chris Harrison]

Hi Boris, I am using the current public stable release (3.6.12)

If I click on the link in comment 12 I cannot go back to this bug page. All the links within the http://ajaxim.com site work but the back button is totally unresponsive until I leave that site or go to a page that doesn't include their chat function. I believe they are using some kind of socket to a server.

I have the same problem on this site which is using the same chat script:
http://propmatch.com.sg

Comment 15

[Boris Zbarsky [:bzbarsky]]

> Hi Boris, I am using the current public stable release (3.6.12)

Ah, ok.  There has been a significant rewrite of history behavior since then, intended precisely to address issues like the one you describe.  I suggest updating to Firefox 4 when it's out.  ;)  And perhaps double-checking that a Firefox 4 beta fixes the issue for you...  I did just verify that I see the problem on that site with 3.6 but not with a current build; both show the chat widget.

Comment 16

[Chris Harrison]

Just a little more information on this bug. It was being caused by a jQuery plugin called 'jsonp'. Whenever this plugin wrote a blank string to an iFrame on the page, Firefox would create a new history item.

More information here:
http://code.google.com/p/jquery-jsonp/issues/detail?id=25

To anyone coming across this bug, the fix is to update to the latest version of the jsonp plugin.