Closed
Bug 1299499
Opened 9 years ago
Closed 9 years ago
Firefox becomes unresponsive if accessing non-remote pages while the RDM is enabled
Categories
(DevTools :: Responsive Design Mode, defect, P1)
Tracking
(firefox48 unaffected, firefox49 unaffected, firefox50 unaffected, firefox51 disabled, firefox52 verified)
VERIFIED
FIXED
Iteration:
52.3 - Nov 14
Tracking | Status | |
---|---|---|
firefox48 | --- | unaffected |
firefox49 | --- | unaffected |
firefox50 | --- | unaffected |
firefox51 | --- | disabled |
firefox52 | --- | verified |
People
(Reporter: mboldan, Assigned: jryans)
References
Details
(Whiteboard: [multiviewport] [reserve-rdm])
[Affected versions]:
- Firefox 51.0a1 (2016-08-31)
[Affected platforms]:
- Windows 10x64, Mac OS X 10.10.5, Ubuntu 16.04x64
[Steps to reproduce]:
1. Launch Firefox.
2. From about:config, enable the devtools.responsive.html.enabled pref.
3. Enable RDM.
4. Open non-remote(Eg. about:config) page the opened tab.
5. Select another tab.
6. Click on the previous tab.
[Expected result]:
- Firefox works correctly.
[Actual result]:
- Firefox becomes unresponsive and in the Browser Console, the Error: Assertion failuretabbrowser.xml:3545:23 is thrown.
[Regression range]:
- I will search for regression ASAP.
[Additional notes]:
- Also, after performing step 4 from STR, the RDM tool is displayed as being enabled in the Developer menu.
Reporter | ||
Updated•9 years ago
|
QA Whiteboard: [qe-rdm]
Updated•9 years ago
|
Flags: qe-verify+
Priority: -- → P3
Whiteboard: [multiviewport] [triage] → [multiviewport] [reserve-rdm]
![]() |
||
Comment 1•9 years ago
|
||
Regression window:
https://hg.mozilla.org/integration/fx-team/pushloghtml?fromchange=6de5b59dbcf95bb561d3c60f63743311f3f5d653&tochange=59bc5cd1caa619e2be168d5fa67803f9e96c4309
Triggered by: Bug 1240900
Blocks: 1240900
Keywords: regressionwindow-wanted → regression
Assignee | ||
Updated•9 years ago
|
Blocks: enable-rdm
Assignee | ||
Comment 3•9 years ago
|
||
(In reply to Gerry Chang [:gchang] from comment #2)
> Hi :jryans,
> Can you help take a look at this bug?
Yes, we'll get to this as part of our prioritized bug list for this new feature. I'll remove regression keyword since it confuses tracking for a feature that's not yet enabled.
Is there a specific reason you're calling out this bug, or just because it was marked as a regression?
Flags: needinfo?(jryans)
Keywords: regression
Assignee | ||
Updated•9 years ago
|
Assignee | ||
Updated•9 years ago
|
Assignee: nobody → jryans
Status: NEW → RESOLVED
Closed: 9 years ago
Priority: P3 → P1
Resolution: --- → FIXED
Updated•9 years ago
|
Iteration: --- → 52.3 - Nov 7
Reporter | ||
Comment 5•9 years ago
|
||
The issue is no longer reproducible on Firefox 52.0a1 (2016-10-23).
The tests were performed under Windows 10x64, Mac OS X 10.11.6, Ubuntu 16.04 x64.
Updated•7 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•