[Firefox Nightly] if I made changes and try to refresh the page in responsive mode, it doesn't update content
Categories
(DevTools :: Responsive Design Mode, defect, P2)
Tracking
(Not tracked)
People
(Reporter: aakirachan, Assigned: bradwerth)
References
(Blocks 1 open bug)
Details
(Whiteboard: [dt-q])
Attachments
(4 files, 1 obsolete file)
Updated•6 years ago
|
Comment 11•6 years ago
|
||
Reporter | ||
Comment 12•6 years ago
|
||
Reporter | ||
Comment 13•6 years ago
|
||
Comment 15•6 years ago
|
||
Reporter | ||
Comment 17•6 years ago
|
||
Comment 19•6 years ago
|
||
Comment 20•6 years ago
|
||
Comment 22•6 years ago
|
||
Assignee | ||
Updated•6 years ago
|
Comment 23•6 years ago
|
||
Updated•6 years ago
|
Comment 25•6 years ago
|
||
Comment 26•6 years ago
|
||
Comment 27•6 years ago
|
||
Comment 29•6 years ago
|
||
Comment 30•6 years ago
|
||
Comment 31•6 years ago
|
||
Comment 32•6 years ago
|
||
Updated•6 years ago
|
Comment 33•6 years ago
|
||
Assignee | ||
Comment 34•6 years ago
|
||
I can replicate, and I have some insight into what's going on, and I have a workaround, but not yet a fix.
First, the workaround: If this happens to you, switching to another tab and then back to the RDM tab should restore your ability to resize the RDM viewport.
What appears to be happening is that, on reload, the presShell of the RDM tab is hitting PresShell::SetIsActive(false) from a style flush. This is deactivating the ability of tab to respond to resize events. I'm not sure why this is happening, but it doesn't get activated again until something like a tab switch happens. I should be able to figure out what's going on by digging into the "normal" reload behavior that occurs without the intervening tab switch.
Assignee | ||
Comment 35•6 years ago
|
||
This appears to have been fixed by the fix for Bug 1441935, which just landed. I can no longer reproduce it. Can you please confirm the fix in current Nightly?
Assignee | ||
Updated•6 years ago
|
Reporter | ||
Comment 36•6 years ago
|
||
(In reply to Brad Werth [:bradwerth] from comment #35)
This appears to have been fixed by the fix for Bug 1441935, which just landed. I can no longer reproduce it. Can you please confirm the fix in current Nightly?
Hi, I tried to reproduce it all morning until now and I couldn't. It seems like it was actually fixed!
Thank you Brad!
Assignee | ||
Updated•6 years ago
|
Comment 37•6 years ago
|
||
In my opinion problem still occurs.
Comment 38•6 years ago
|
||
In my case, the issue was partially fixed. It seems fixed when following the original steps to reproduce mentioned in comment #11.
But if, after repeating those steps a few times, I go to another website (i.e. change the url in the same tab), then the problem happens again: the tab content stays "frozen" with the previous website.
Comment 39•6 years ago
|
||
- 1,
The problem is not fixed.
When responsive view is opened and i go to another page on same website (click link) it does not show next page,
but if i go to another tab and than come back - it shows the new page.
FF 65.0 (64-bit)
Windows 10
Assignee | ||
Comment 40•6 years ago
|
||
I'll try the new Steps to Reproduce.
Assignee | ||
Comment 41•6 years ago
|
||
I can't reproduce this on Release 65 nor on Nightly 67. However, I am testing on macOS and this may be platform-specific. Would you please attempt to reproduce on Nightly? If you are unable to reproduce on Nightly, then this may be hitting a related case that is fixed by Bug 1502909 (fixed for all platforms, we hope).
Comment 42•6 years ago
|
||
I just tried latest nightly and couldn't reproduce the issue. So it seems it has been fixed.
Comment 43•6 years ago
|
||
Given the descriptions that people have been giving for this problem here, it looks like this is a duplicate of bug 1502909.
This is a rendering issue where the content in RDM appears to be frozen until you switch tabs and come back again.
This was introduced in 64 and fixed in 66.
Now, 65 is in release now, so it does have the problem unfortunately, but applying the fix from 66 (in beta) to 65 (in release) was discussed and the idea discarded. It's just too complex and risky.
So we unfortunately have to live with this problem for a few more weeks until 66 makes it to release (4,5 weeks to be precise).
Assignee | ||
Updated•6 years ago
|
Description
•