Google won't entertain user requests

>Seriously, who submits feature requests with language like "the design must be changed" and "this is wrong?"

I don't know. Perhaps the awkward phrasing points to non-native speakers. I know a few people who phrase comments this way, and often they're just translating literally from their native language.

>The entitlement from some of the people in that thread is insane.

That is not a display of entitlement at all.

Users complaining about changes in a product that they do not like is a good thing and must be encouraged. If nobody says anything and just "takes it" things will stay the same. How much weight you want to give to those comments can be argued. Certainly much like in the case of restaurant reviews, a vocal minority can be negative, but you can take them with a grain of salt.

Sums up so many interactions between devs and users...

I think that explanation would be new edge cases for the risk of fullscreen sites impersonating the desktop?

When I worked on bugs I would always be careful to note that kind of reason even if I was a little too terse for the users.. I'd hate to see the motivated new hire try to improve ease of use by examining closed bugs like this one.

If you've been a dev, you know that users want all sorts of things. They are generally awful. Devs may have a long-term plan that they are executing to, or a design template they conform to, or any number of things the user doesn't know about. When users start listing chapter-and-verse how the product should work, its not helpful.

A real report would have said something like "No way to enter a url on fullscreen tab". That might have survived 'bug triage'.