1287808 - The tab mute/unmute button is not working while RDM is enabled

Status: NEW

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

Description

[Mihai Boldan, Desktop QA [:mboldan]]

[Note]:
- Logged based on Bug 1240900 Comment 32

[Affected versions]:
- Firefox 50.0a1 (2016-07-18)

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

[Steps to reproduce]:
1. Launch Firefox.
2. From about:config, enable the devtools.responsive.html.enabled pref.
3. Enable RDM.
4. Go to https://www.youtube.com/ .
5. Click on a video and observe the tab mute button.

[Expected result]:
- The tab mute button is visible and functional.

[Actual result]:
- The tab mute button is not visible.

[Regression range]:
Last good: 2016-04-06
First bad: 2016-04-07
Pushlog: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=68c0b7d6f16ce5bb023e08050102b5f2fe4aacd8&tochange=8fc46323cee61bddc4c38701d6020379bba5774a

[Additional notes]:
- Note that the mute/unmute tab button is visible if the RDM is disabled and re-enabled after performing the STR, but the button is not working.

Comment 1

[ovidiu boca[:Ovidiu]]

I talked with Ryan VanderMeulen on IRC and he thinks this is a regression from bug 1240896, also he suggested to ni? :jryans because this seems pretty important.

Comment 2

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

(In reply to ovidiu boca[:Ovidiu] from comment #1)
> I talked with Ryan VanderMeulen on IRC and he thinks this is a regression
> from bug 1240896, also he suggested to ni? :jryans because this seems pretty
> important.

It is currently expected that various browser features aren't yet working in the new RDM.  The new RDM is not yet enabled by default, so this issue and various others like it aren't exposed to users yet.  For this reason, it's not important to uplift anything here.

It's definitely important to have them on file though so we can be aware of them. 

Once we eventually enable the new RDM that uses this path, the situation changes, and it would make sense to track new ones as regressions, uplift fixes where possible, etc.

I don't think it's useful to block bug 1240896 or treat this as regression at the current time.

Comment 3

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

Bug in disabled feature under development, removing regression keyword.