Suggested severity

• S2

Affected versions

• 80.0b1

Affected platforms

• Windows 10x64
• Windows 7x64
• Ubuntu 18.04x64

Steps to reproduce

1. Launch Firefox.
2. Go to facebook.
3. Play a random video from the news feed.
4. Try to change the volume level.

Expected result

• The video volume is successfully changed.

Actual result

• The video is muted and can be unmuted just if you click the volume icon.

Regression range

• I’ll come with a regression asap. But from what I’ve checked something is broken between 79.0b9 and 80.0b1, because the rc 79.0 build and 79.0b9 are not affected.

Additional notes

• see the screen record https://drive.google.com/file/d/16JFgFDw57m84DOo6WsjHCt4Ms_IrSAJc/view?usp=sharing
• this issue isn’t reproducible on latest nightly (81.0a1 2020-07-28) or on latest rc (79.0) build.
• if the video is opened from watch section, works fine.

Hello,

I searched for a regression interval using mozregression and received this pushlog https://hg.mozilla.org/releases/mozilla-beta/pushloghtml?fromchange=ed642a962c257415731c43192ae769901d69630d&tochange=47781f2219f0fbb444f8f13d3b62d85dd7a191eb

Because the problem is only reproducible in beta and given that this problem only occurs from the first beta of this cycle, the number of potential regressors is large so I'm not sure which one caused this issue.

Changing the flag for 81 as unaffected, because this issue is reproducible only on beta 80. If the reason of marking it as affected was another feel free to change it again.

Thanks.

I'd rather we understood what the difference is here between nightly and beta, and why it's not going to bite us when 81 goes to beta. Can you reproduce this with 80 nightly builds?

In nightly 80 from 27.07.2020 this issue is reproducible. I've ran a find fix bisection and returned this pushlog https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=eba7e3ce93822075543bcc764cef7dbc8e9fc5f1&tochange=2f8d4f1f660836c1c7b71a573dfe015694d30c86

Thank you. Not quite sure what in there would explain this unfortunately :/

I've launched again a find fix bisection just to be sure and obtained this pushlog https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=51da3f1e63df8830d3d1149b9ded1159b53aef3e&tochange=1fa3c63f82d23ea49809c70a74bea90a8fd6f426

Oh good. Bug 1655398 is about to land on beta, so hopefully we can verify the fix there too.

:mberlinger, since this bug is a regression, could you fill (if possible) the regressed_by field?
For more information, please visit auto_nag documentation.

Has this been fixed?

Hello,

Looks like bug 1655398 might have fixed this one since I can't reproduce anymore using 80.0b3 on the following OSes: Windows 10x64, Windows 7x64 and Ubuntu 18.04X64, marking this as wfm.