3 ms·

I don't think your theory fits the facts... The bug is from 2018, and was fixed three years later. So it doesn't seem like there was any kind of special priori

by jsnell 5y ago

I don't think your theory fits the facts... The bug is from 2018, and was fixed three years later. So it doesn't seem like there was any kind of special prioritization going on here. It was also fixed by a person working at Microsoft, not by somebody at Google.

josephcsible 5y ago
I think the point that was if anyone but Google wanted this, it'd get laughed all the way to WONTFIX.
- judge2020 5y ago
  As shown in the changelog, the bug was filed by a user @amplifiedit.com, and was seen as a worthwhile bug to fix by Brian Malcolm "Taking ownership as the client team in BVE will work on this item"[0]; however, it was stalled for nearly 3 years until Eric submitted a patch for it[1]. While Google thinks it's worthwhile to fix, Microsoft is trying to have a faster-than-usual rise in adoption for their new Edge which is based on Chromium, so that means fixing as many things as possible that their business/EDU customers complain about. BTW Google already allowed MDM (device) admins to disable devtools, but everyone involved in the issue also wanted it to disable view-source since it allowed students to look at the HTML. 0: https://bugs.chromium.org/p/chromium/issues/detail?id=895462#c35 https://bugs.chromium.org/p/chromium/issues/detail?id=895462... 1: https://bugs.chromium.org/p/chromium/issues/detail?id=895462#c54 https://bugs.chromium.org/p/chromium/issues/detail?id=895462...
- jsnell 5y ago
  Yes, I understand that's that was the point. But again, Google clearly didn't actually particularly want this since nobody from that company actually worked on this bug during the three years it was open. Your suggestion seems equally invalid. The Chromium bug tracker currently has about 9k open feature requests. A lot of them are more niche than this, have no indication on the bug that they're relevant to Google, and have still not been closed as WONTFIX. So it really was not a valid point to start with, and I don't understand why you're doubling down on it like that.

by jsnell 5y ago

josephcsible 5y ago

I think the point that was if anyone but Google wanted this, it'd get laughed all the way to WONTFIX.

judge2020 5y ago
As shown in the changelog, the bug was filed by a user @amplifiedit.com, and was seen as a worthwhile bug to fix by Brian Malcolm "Taking ownership as the client team in BVE will work on this item"[0]; however, it was stalled for nearly 3 years until Eric submitted a patch for it[1]. While Google thinks it's worthwhile to fix, Microsoft is trying to have a faster-than-usual rise in adoption for their new Edge which is based on Chromium, so that means fixing as many things as possible that their business/EDU customers complain about. BTW Google already allowed MDM (device) admins to disable devtools, but everyone involved in the issue also wanted it to disable view-source since it allowed students to look at the HTML. 0: https://bugs.chromium.org/p/chromium/issues/detail?id=895462#c35 https://bugs.chromium.org/p/chromium/issues/detail?id=895462... 1: https://bugs.chromium.org/p/chromium/issues/detail?id=895462#c54 https://bugs.chromium.org/p/chromium/issues/detail?id=895462...
jsnell 5y ago
Yes, I understand that's that was the point. But again, Google clearly didn't actually particularly want this since nobody from that company actually worked on this bug during the three years it was open. Your suggestion seems equally invalid. The Chromium bug tracker currently has about 9k open feature requests. A lot of them are more niche than this, have no indication on the bug that they're relevant to Google, and have still not been closed as WONTFIX. So it really was not a valid point to start with, and I don't understand why you're doubling down on it like that.