Closed
Bug 816209
Opened 12 years ago
Closed 4 years ago
yesplanet.co.il loads slow: unresponsive script
Categories
(Firefox for Android Graveyard :: Toolbar, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: ogirtd, Unassigned)
References
Details
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:17.0) Gecko/17.0 Firefox/17.0
Build ID: 20121120042814
Steps to reproduce:
go to www.yesplanet.co.il - the site is loading extremely slow, followed by a "unresponsive script" dialog.
Comment 1•12 years ago
|
||
Thanks for the bug report. The site looks heavily optimized for desktop, I was able to reproduce on my Galaxy Nexus (Android 4.2.1) with Nightly (20.0).
Comment 2•12 years ago
|
||
Note that there doesn't seem to be any problem loading the site on the stock Android browser, or on iPhone.
Comment 3•12 years ago
|
||
I still see this and still get the slow-script warning dialog, Kevin/Kats, can this be profiled?
Status: UNCONFIRMED → NEW
Component: General → Graphics, Panning and Zooming
Ever confirmed: true
OS: Linux → Android
Hardware: x86 → ARM
Version: Firefox 17 → Trunk
Comment 4•12 years ago
|
||
I tried profiling it but didn't get very far. I've filed bug 840095 for profiler improvements that might help here.
Comment 5•4 years ago
|
||
We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → INCOMPLETE
Updated•4 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•