- First of all: I understand that this is a known (closed) bug in every upstream mentioned, but, please, see more below. And I also understand that GNOME Web/Epiphany maybe is not the ideal target for a patch; if it's not, please, just change to a more appropriate component.
- BUT, the point is: this is a really, really, really, really bad experience, and, since none of the upstreams want/can fix it, it's probably a good candidate for a downstream patch, I'm right?
# Description of problem:
Some(1) webpages, when playing some(2) audio (or video/audio), can disrespect user choosen max main volume e set it to 100%(3).
1- Or all webpages?
2- Or just HTML 5 audio (video/audio)?
3- Sometimes happens with smaller values. Not sure what "holds" the limit, though.
# Version-Release number of selected component (if applicable):
# Steps to Reproduce:
1. Set main volume (in GNOME Shell) to something less than 100%.
2. Open GNOME Web.
3. Go to https://www.youtube.com/
4. Click on any video and notice the volume instantly raising.
# Expected results:
GNOME Web honor user setted max global volume.
# Actual results:
GNOME Web going insane and giving free hearing damage and heart attacks to everyone :P
Although I'm kidding (and I'm not a doctor), I would insist that (besides a horrible user experience) these two extreme and unlikely situations can still happen if leaded by powerful headphones, or a bad heart condition, or both; I'm wrong?
Created attachment 1049679 [details]
Screencast of the bug.
Once that API becomes available, then it will be possible to fix this in WebKit. We have an upstream bug for this: https://bugs.webkit.org/show_bug.cgi?id=140358
Until then, the only solution is to disable flat volumes: https://wiki.archlinux.org/index.php/PulseAudio/Troubleshooting#Per-application_volumes_change_when_the_Master_volume_is_adjusted
Ok, sorry for the extra downstream "noise" :/
And thank you for your time and patience, Michael.
I will try the flat thing, meanwhile, to see if I can give Web a bit more of usage, anyway.
*** This bug has been marked as a duplicate of bug 1265267 ***