Closed
Bug 1510540
Opened 6 years ago
Closed 5 years ago
In Responsive Design Mode, JavaScript running is slowed down to a crawl after switching to a different tab
Categories
(DevTools :: Responsive Design Mode, defect, P3)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: elmo.allen, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [dt-q])
Attachments
(2 files)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:64.0) Gecko/20100101 Firefox/64.0
Steps to reproduce:
In Responsive Design Mode, the JavaScript engine seems to slow down considerably, if I switch to a different tab in the browser and then come back. The problem goes away if I close and reopen the RDM.
I made a short test HTML with quick & dirty JavaScript. When you click the top element, it runs a function with setInterval that changes its height. The bottom element was to test if it affects CSS transitions, but doesn't seem to.
To reproduce:
1. Open the attached HTML.
2. Invoke Responsive Design Mode.
3. Open a new tab (no need to browse on any page with it).
4. Come back to the tab with the RDM.
5. Click the element "Toggle: JavaScript animation"
You can see the animation happening at a rate of 1 to 2 ticks per second, when it should happen every 25 millisecond. If you now close & reopen the RDM and then reload the page and click the element again, you'll see it moving at the intended smooth growing rate.
If now, after getting the initial bug to show, I reload the page, the rendering seems to stuck completely, even the CSS transitions stop working. If I then switch to a different tab and back, the rendering again continues, but with the initial bug.
This doesn't seem to happen in the 63 version, only in the 64.
Reporter | ||
Comment 1•6 years ago
|
||
Weirdly enough, this doesn't seem to happen if the tab switch is very quick, something like under half a second. If I stay on the different tab for at least one or two seconds, the bug happens. With the quick tab switch back and forth I can sometimes even get it to again working normally, but not all the time.
Reporter | ||
Comment 2•6 years ago
|
||
Now my "normal" Firefox updated from 63 to 64.0, and now this bug started occurring in it as well, where before this it didn't occur. In my Dev browser, now 65.0b2, it still happens as well.
Comment 3•6 years ago
|
||
I can reproduce this issue as long as the newly created tab stays open.
Note that not only is the animation slow, but also the browser navigation does not react anymore. See the video attached where I try to use the back button and it only reacts when I toggle RDM off again (or close the new tab)
Updated•6 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: -- → P2
Whiteboard: [dt-q]
Comment 4•6 years ago
|
||
Do we know anything about the cause or even better: how to fix? That's the most annoying issue when developing websites in Firefox. And as a frontend developer that's what I do all the day. :)
Reporter | ||
Comment 5•6 years ago
|
||
I haven't tested this for a while, but it seems that at least on 67.0b1 I cannot reproduce this issue. The 65.0.2 (I believe the latest published version) still does it. Didn't test this on 66.x.
Updated•6 years ago
|
Whiteboard: [dt-q] → [rdm-mvp] [dt-q]
Comment 6•6 years ago
|
||
I can't reproduce. Is it still occurring for you?
Flags: needinfo?(elmo.allen)
Updated•6 years ago
|
Priority: P2 → P3
Whiteboard: [rdm-mvp] [dt-q] → [rdm-reserve] [dt-q]
Reporter | ||
Comment 7•5 years ago
|
||
(In reply to Brad Werth [:bradwerth] (PTO until 7/29) from comment #6)
I can't reproduce. Is it still occurring for you?
Like I said in the comment above, after the version 67.x I cannot reproduce it any more.
Flags: needinfo?(elmo.allen)
Updated•5 years ago
|
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WORKSFORME
Updated•5 years ago
|
Whiteboard: [rdm-reserve] [dt-q] → [dt-q]
You need to log in
before you can comment on or make changes to this bug.
Description
•