This issue is reported many times and marked as wontfix by dev. You can find the bug details here https://bugs.chromium.org/p/chromium/issues/list?can=1&q=reporter%3Anicsplatts%40gmail.com&colspec=ID+Pri+M+Stars+ReleaseBlock+Component+Status+Owner+Summary+OS+Modified&x=m&y=releaseblock&cells=ids.

As CL and obsrvations are already given in https://bugs.chromium.org/p/chromium/issues/detail?id=793607#c7 ,removing Needs-Bisect label.

Could someone from Internals>Media team take a look at this issue.

Thanks!

Thank you for noticing. 

Many others and myself have provided plenty feedback and demand to resolve this behavior, but as you can see every bug I or others have opened, the dev has closed as wont fix, without providing any reasoning, other than "because I want to" while demanding more feedback from us. When asked to help us with a workaround or a solution or any help, they go silent. When the requested feedback is given, they go silent.  

Read all the comments in  bug 728108 . Clearly we ALL want this behavior back, and a single dev is blocking us with no reasoning provided.

On the issues that were closed as wontfix, we have been asking for input from the developers and they have failed to respond or justify why this cannot or should not be fixed. 

Users continue to ask for this to be fixed with no feedback or support. 

Merry Christmas everyone.

I have still been asking in the other bugs for any feedback that can validate their decision to not fix this, and they still fail to respond. 

More users continue to ask for this to be fixed.

Thank you

Kindly still waiting for any assistance : (

:(

This issue seems to be out of scope for triaging from TE-end as the reporter is asking a specific behaviour to be brought back/re-enable, Hence requesting someone from "Internals>Media" team to have a look into it for further investigation. Adding label TE-NeedsTriageHelp.

OP has been (re-)opening bugs for a feature do not intend to support. It was available behind a chrome://flags but chrome://flags are not meant to be used as settings and are not supported features. We had data about the usage of this feature and it was quite low. It wouldn't make sense to add a setting for it product-wise. Especially, seeing that websites were suggesting their users to enable this flag was fairly scary for a feature we never intended to really support.

You took away behavior we wanted, then broke the flag.

I will keep opening bugs until it's fixed

Oh yeah so because a majority doesn't like it we can screw over the people who want it.

The fact a larger group didn't use it than a group that did does not justify removing this behavior or ability. Settings exist to give users an option and be happy. You are taking away an ability from a still fairly large amount of users and making them unhappy.

You've made me the most unhappy, so I will be here until this gets fixed. Thanks

#10 - I strongly advise you not to create more and more issues, because I guess you will be blocked at some point or it will simply be an unnecessary and time consuming (for everyone involved, including you) cat-and-mouse game.

Note that Chrome generally caters for the majority. It does not make sense to give budget to develop features used by minorities, or confuse the user with even more options.

I will keep creating bugs and some day someone will finally listen

If I have to make a vpn and new accounts to keep filing them, I will do so

I refuse to let this happen without a fight. Can you clearly not see how important this is?