1298811 - The Developer Toolbar is dismissed and no longer can be accessed if the browser is restarted while the RDM is enabled

Status: RESOLVED DUPLICATE of bug 1319596

(DevTools :: Responsive Design Mode, defect, P3)

Description

[Mihai Boldan, Desktop QA [:mboldan]]

[Note]:
- Logged based on Bug 1250091 Comment 7

[Affected versions]:
- Firefox 51.0a1 (2016-08-29)

[Affected platforms]:
- Windows 7 x64, Mac OS X 10.10.5, Ubuntu 16.04 x64

[Steps to reproduce]:
1. Launch Firefox.
2. From about:config, enable the devtools.responsive.html.enabled pref.
3. Open Developer Toolbar and restart the browser using the restart command.
4. Select one of the already opened tabs.
5. Enable RDM.
6. Restart the browser using the 'restart' command in the Developer Toolbar.

[Expected result]:
- The page is restarted with the RDM disabled and with the Developer Toolbar enabled.

[Actual result]:
- The browser is restarted and the Developer toolbar is no longer displayed. Also in Menu->Developer, the Developer Toolbar is checked, as it is enabled. (here is a screencast with the bug: https://drive.google.com/file/d/0B-cUbHVNThEKZjhmRFBlRmQ5Tnc/view)

[Regression range]:
- I will check if this is a regression asap.

[Additional notes]:
- Note that the Developer Toolbar can't be opened after restarting FF.

Comment 1

[YF (Yang)]

I found the regression range:
https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=a524931c115bd49b76786d29e9231be458d95d78&tochange=84e635f18d703b7e359df0b38de10b892a852718

And it's Depends on: bug 1310771. I guess this is a dupe of it.

Comment 2

[J. Ryan Stinnett [:jryans] (Use needinfo, replies may be slow)]

(In reply to YF (Yang) from comment #1)
> I found the regression range:
> https://hg.mozilla.org/integration/mozilla-inbound/
> pushloghtml?fromchange=a524931c115bd49b76786d29e9231be458d95d78&tochange=84e6
> 35f18d703b7e359df0b38de10b892a852718
> 
> And it's Depends on: bug 1310771. I guess this is a dupe of it.

I am perplexed by this comment...  It seems to suggest bug 1310771 fixed this issue?  But then it was marked as a duplicate of bug 1319596 instead.  Do you know which bug really has the fix?

Comment 3

[YF (Yang)]

(In reply to YF (Yang) from comment #1)
> And it's Depends on: bug 1310771. I guess this is a dupe of it.

* And it's Depends on: bug 1319596.

I think bug 1319596 has fixed this bug, based on my previous tests.