Fails to load data from ebay page with "back"




Document Navigation
12 years ago
10 months ago


(Reporter: Wm Neal Harmon, Unassigned)


Windows XP

Firefox Tracking Flags

(Not tracked)


(Whiteboard: [platform-rel-eBay], URL)



12 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060426 SeaMonkey/1.5a
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060426 SeaMonkey/1.5a

Cursing around ebay.  I hit the back button and all I got was the very header (tow top lines) copy stoped after the "Buy / Sell / My Ebay /etc" line.  Blank, white screen.  If I hit "reload" it comes back but if I go forward and back, it does it again

Reproducible: Always

Steps to Reproduce:
1.Login to and go to an item / auction description and then another, like in two or three items, maybe look at other stuff the seller has.
2.Hit the <<back>> button to go back one screen.
3.It DOES go back, but only the top two lines of copy are displayed.

Actual Results:  
Mostly white screen withthe ebay logo and the "Buy / Sell / My Ebay / etc" block/bottons are visible, the rest is somewhere else.

Expected Results:  
Full screen image that had been displayed before.

If to hit <<refresh>> it will refresh and paint the screen correctly.


12 years ago
Assignee: general → nobody
Component: General → History: Session
Product: Mozilla Application Suite → Core
QA Contact: general → history.session
Version: unspecified → Trunk


10 years ago
Component: History: Session → Document Navigation
QA Contact: history.session → docshell
platform-rel: --- → ?
Whiteboard: [platform-rel-eBay]
platform-rel: ? → ---

Comment 1

10 months ago
I've gotten this problem about 10 times since I installed FF54 on my Windows Desktop PC. The problem is on every Windows I have: 7, 8 and 10. In general Ebay shopping site stopped working since FF54 was installed on my PC. Hitting the "Back" button gives me a blank page, and reload starts the throbber going but a page never reloads.
You need to log in before you can comment on or make changes to this bug.