5 ms·

The chromium bug from the TFA [1] only has 76 comments, as of writing this. Seventy six. Out of millions of users. And of those 76, it's not all pro-revert rh

The chromium bug from the TFA [1] *only* has 76 comments, as of writing this. Seventy six. Out of millions of users. And of those 76, it's not all pro-revert rhetoric. Any outrage here caused by the upstream changes seems quite hyperbolic. As a user, I'm annoyed my browser will now be subject to a flawed implementation for however much longer it now takes to revert the reversion (de-facto standard or not). I most certainly can't be alone in this stance. While I empathize a subset of developers may have been caught off guard by changes, my empathy has limits: their inconvenience is not worth my browser safety. Why must users suffer at the hand of a few chest-thumping devs? A little deference for history I think would also go a long way here: time and again Google has to kick the industry hard in it's complacency [2][3]. How quickly the industry seems to have forgotten that not all that long ago, developers [and administrators] had to be dragged kicking and screaming like toddlers, to support HTTPS adoption (and corresponding changes to the chrome UI). Was that change difficult then? You bet. Was it a net-good change in the long run? Hell yes. As Bruce Wayne said to Alfred after laying waste to League of Shadow's headquarters in Nolan's Batman Begins: "People need dramatic examples to shake them out of apathy [...]" Chrome Security team, if you're reading this, keep on trucking. - [1] https://bugs.chromium.org/p/chromium/issues/detail?id=1065085 https://bugs.chromium.org/p/chromium/issues/detail?id=106508... - [2] https://bugs.chromium.org/p/chromium/issues/detail?id=1065085#c69 https://bugs.chromium.org/p/chromium/issues/detail?id=106508... - [3] https://security.googleblog.com/2018/02/a-secure-web-is-here-to-stay.html https://security.googleblog.com/2018/02/a-secure-web-is-here...

toyg 5y ago
The HTTPS adoption switch worked only because Let's Encrypt happened. Otherwise people would have screamed blue murder.
edent 5y ago
How many of those millions of users know where to report a bug? How many of those who know, have reported or commented on bugs which have never been fixed?
vasachi 5y ago
Yes, please, make my browsing more secure by removing first party alerts. So much security will be achieved /s
- staticassertion 5y ago
  It's explicitly cross-origin.
  - asddubs 5y ago
    They're planning to get rid of first party alerts as well, it says so in the article. And in the meantime, there's no way to opt out of breaking cross-origin alerts, which is not great for things like codepen.
phpnode 5y ago
Do you have any idea how much of the web will break if alert(), confirm() and prompt() are removed? Tens of millions of websites, many of which are no longer maintained will stop working. This is the destruction of the web over a UX issue - fix the UX issue, don't break the web! Those functions should be deprecated and new applications should be discouraged from using them, but they should never be removed.
- torstenvl 5y ago
  Any part of the web that requires JavaScript to work, let alone that married itself to a particular version of JavaScript, was broken ab initio.
  - phpnode 5y ago
    You would rather move the goal posts than acknowledge the issue?
veeti 5y ago
> Why must users suffer at the hand of a few chest-thumping devs? The only suffering here is at the hands of the Chrome developers, who apparently feel entitled to break extremely widely used features that have worked perfectly fine for the past 20+ years. This change broke Salesforce [1] among many others: that's literally millions of affected users. And I can promise you that not one of them cares about Chrome's internal implementation details. [1] https://help.salesforce.com/articleView?id=000362676&language=en_US&mode=1&type=1 https://help.salesforce.com/articleView?id=000362676&languag...
matkoniecz 5y ago
> has 76 comments, as of writing this. Seventy six. Out of millions of users. I just commented in https://github.com/whatwg/html/issues/6897#issuecomment-893361417 https://github.com/whatwg/html/issues/6897#issuecomment-8933... and https://github.com/whatwg/html/issues/2894#issuecomment-893365430 https://github.com/whatwg/html/issues/2894#issuecomment-8933... - and even that is too much given that I am using my unpaid hobby time for it. I am not getting paid for it unlike some people in Google that try to remove alert() and break stuff for everyone instead of fixing bad UI of their browser.

The chromium bug from the TFA [1] *only* has 76 comments, as of writing this. Seventy six. Out of millions of users. And of those 76, it's not all pro-revert rh

toyg 5y ago

The HTTPS adoption switch worked only because Let's Encrypt happened. Otherwise people would have screamed blue murder.

edent 5y ago

How many of those millions of users know where to report a bug? How many of those who know, have reported or commented on bugs which have never been fixed?

vasachi 5y ago

Yes, please, make my browsing more secure by removing first party alerts. So much security will be achieved /s

staticassertion 5y ago
It's explicitly cross-origin.
- asddubs 5y ago
  They're planning to get rid of first party alerts as well, it says so in the article. And in the meantime, there's no way to opt out of breaking cross-origin alerts, which is not great for things like codepen.

phpnode 5y ago

Do you have any idea how much of the web will break if alert(), confirm() and prompt() are removed? Tens of millions of websites, many of which are no longer maintained will stop working. This is the destruction of the web over a UX issue - fix the UX issue, don't break the web! Those functions should be deprecated and new applications should be discouraged from using them, but they should never be removed.

torstenvl 5y ago
Any part of the web that requires JavaScript to work, let alone that married itself to a particular version of JavaScript, was broken ab initio.
- phpnode 5y ago
  You would rather move the goal posts than acknowledge the issue?

veeti 5y ago

> Why must users suffer at the hand of a few chest-thumping devs? The only suffering here is at the hands of the Chrome developers, who apparently feel entitled to break extremely widely used features that have worked perfectly fine for the past 20+ years. This change broke Salesforce [1] among many others: that's literally millions of affected users. And I can promise you that not one of them cares about Chrome's internal implementation details. [1] https://help.salesforce.com/articleView?id=000362676&language=en_US&mode=1&type=1 https://help.salesforce.com/articleView?id=000362676&languag...

matkoniecz 5y ago

> has 76 comments, as of writing this. Seventy six. Out of millions of users. I just commented in https://github.com/whatwg/html/issues/6897#issuecomment-893361417 https://github.com/whatwg/html/issues/6897#issuecomment-8933... and https://github.com/whatwg/html/issues/2894#issuecomment-893365430 https://github.com/whatwg/html/issues/2894#issuecomment-8933... - and even that is too much given that I am using my unpaid hobby time for it. I am not getting paid for it unlike some people in Google that try to remove alert() and break stuff for everyone instead of fixing bad UI of their browser.