Yeah, this has been my thought ever since the first time I saw javascript that disabled right click. There were workarounds, but I thought the browser shouldn’t even try to cooperate with something like that.
These days, it’s sites that disable scrolling. Sure, I can fuck with the css to enable it again, but it should be a menu option or just not something that can be disabled in css or via js.
Same for all of the other metrics that browsers send in the headers. Even though it’s nice to see stats on OS use and such, why does a server need to know which one I’m using? Even for screen resolution, while you could say that it affects how the page should be rendered, I’d prefer a standardized bug reporting mechanism for letting webmasters know when their page is broken for a certain resolution and otherwise letting the browser handle the rendering. And if it means the death of sites that cover their page in images to make a fancy layout, tbh good riddance.
Yeah, this has been my thought ever since the first time I saw javascript that disabled right click. There were workarounds, but I thought the browser shouldn’t even try to cooperate with something like that.
These days, it’s sites that disable scrolling. Sure, I can fuck with the css to enable it again, but it should be a menu option or just not something that can be disabled in css or via js.
Same for all of the other metrics that browsers send in the headers. Even though it’s nice to see stats on OS use and such, why does a server need to know which one I’m using? Even for screen resolution, while you could say that it affects how the page should be rendered, I’d prefer a standardized bug reporting mechanism for letting webmasters know when their page is broken for a certain resolution and otherwise letting the browser handle the rendering. And if it means the death of sites that cover their page in images to make a fancy layout, tbh good riddance.