Closed Bug 877241 Opened 7 years ago Closed 7 years ago

Defect - leaving autoblog.com page open for a while makes Metro Firefox unresponsive

Categories

(Firefox for Metro Graveyard :: General, defect, P1)

x86
Windows 8.1
defect

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: jbecerra, Unassigned)

References

Details

(Keywords: perf, Whiteboard: feature=defect c=browsing u=metro_firefox_user p=0)

Tested on 2013-05-29 using latest nightly.

I've noticed this for a while. When I have the autoblog.com page open, and I leave it idle for a little while, when I go back to it and try ctrl-l to get the navigation bar, it takes several seconds before it is shown.

Steps:
1. Go to autoblog.com
2. Leave it there fore a few minutes (5mins is fine).
3. Swipe up from the bottom or ctrl-l to bring up the navigation bar.

Expected: You see the navigation bar right away, so that you can start typing the URL to another site.

Actual: Nothing happens for seconds.
Keywords: perf
Whiteboard: feature=defect c=tbd u=tbd p=0
General performance on this site is crummy. Desktop doesn't have any issues. My guess is this has to do with a missing flash plugin.
Priority: -- → P1
Summary: defect - leaving autoblog.com page open for a while makes Metro Firefox unresponsive → Defect - leaving autoblog.com page open for a while makes Metro Firefox unresponsive
Whiteboard: feature=defect c=tbd u=tbd p=0 → feature=defect c=content_features u=tbd p=0
Blocks: 887442
Whiteboard: feature=defect c=content_features u=tbd p=0 → feature=defect c=browsing u=metro_firefox_user p=0
WFM in latest nightly. Juan, can you confirm?
Flags: needinfo?(jbecerra)
OS: Mac OS X → Windows 8 Metro
Tested on 2013-07-16 using latest nightly. I opened the site on two machines and let them idle for a while, and when I come back to the page I can scroll, open new tabs, and I don't see any loss of responsiveness.
Status: NEW → RESOLVED
Closed: 7 years ago
Flags: needinfo?(jbecerra)
Resolution: --- → WORKSFORME
OS: Windows 8 Metro → Windows 8.1
You need to log in before you can comment on or make changes to this bug.