Content not refreshing unless another tab is clicked or the page is scrolled up or down.

RESOLVED WORKSFORME

Status

Camino Graveyard
General
--
major
RESOLVED WORKSFORME
10 years ago
10 years ago

People

(Reporter: Steven Hollingsworth, Unassigned)

Tracking

Details

(URL)

(Reporter)

Description

10 years ago
User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en; rv:1.9b3pre) Gecko/2008010500 Camino/2.0a1pre (like Firefox/3.0b3pre)
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en; rv:1.9b3pre) Gecko/2008010500 Camino/2.0a1pre (like Firefox/3.0b3pre)

Images and buttons such as those on the Google Docs Blog (http://googledocs.blogspot.com/2008/01/new-features-for-2008.html) do not refresh as they are changed and have to "manually" be refreshed by clicking on another tab and then going back to the original or scrolling up or down on that page.

Reproducible: Always

Steps to Reproduce:
1. Open http://googledocs.blogspot.com/2008/01/new-features-for-2008.html.
2. Click on the forward or back buttons on the embedded presentation.
3. Watch as the images do not change and have to "manually" be refreshed.
Actual Results:  
The embedded presentation does not change as each slide loads and the image has to be manually refreshed.

Expected Results:  
I expected the slides to change automatically without having to manually refresh the image.
(Reporter)

Updated

10 years ago
Status: UNCONFIRMED → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → WORKSFORME

Updated

10 years ago
Status: RESOLVED → VERIFIED
(Reporter)

Updated

10 years ago
Status: VERIFIED → UNCONFIRMED
Resolution: WORKSFORME → ---

Comment 1

10 years ago
This WFM in recent trunk. Do you see this in a recent build, and if so does it work for you in Minefield?
(Reporter)

Updated

10 years ago
Status: UNCONFIRMED → RESOLVED
Last Resolved: 10 years ago10 years ago
Resolution: --- → WORKSFORME
(Reporter)

Comment 2

10 years ago
This was reopened by mistake. This WFM in the latest nightly of Camino and Minefield.
You need to log in before you can comment on or make changes to this bug.