11–20 of 136 posts
What are the implications of this? Can’t you just curl/wget the html?
Some more context at https://bugs.chromium.org/p/chromium/issues/detail?id=895462 : > With Schools using Google Forms as a testing platform, students are able to use this shortcut to search through the source of the page, and determine the correct answers.
> With Schools using Google Forms as a testing platform, students are able to use this shortcut to search through the source of the page, and determine the correct answers.
That said, I highly doubt that Google would take this feature request seriously if this were not associated with another Google property. For example, I can't imagine that if Typeform users opened a similar bug ticket that it would see any traction. To me this highlights a danger I had not considered before around the monopoly power of Google - inane requests that would benefit properties within the Google ecosystem get undue consideration despite it harming the broader ecosystem.
Why do I feel like everyone will do this in the quest for "protecting ad money" and will once again have the case of that man charged with hacking for doing CTRL+u
Some more context at https://bugs.chromium.org/p/chromium/issues/detail?id=895462 : > With Schools using Google Forms as a testing platform, students are able to use this shortcut to search through the source of the page, and determine the correct answers.
This is for the chromeos devices/managed chrome browsers [1]. From the bug [2] it looks like this was relevant in a school setting, where this is common. So the school hands out some chromebooks and wants to use that managed environment to prevent kids cheating on quizzes by looking at source code. DRM and related technologies are an effort to wrest control of devices away from their owners, and give control the manu…
For context, this is is not allowing websites to prevent View Source for all users. Rather it is a setting that administrators can set on Google Chrome installations within their company/school/etc. That said, I highly doubt that Google would take this feature request seriously if this were not associated with another Google property. For example, I can't imagine that if Typeform users opened a similar bug ticket tha…
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.
Some more context at https://bugs.chromium.org/p/chromium/issues/detail?id=895462 : > With Schools using Google Forms as a testing platform, students are able to use this shortcut to search through the source of the page, and determine the correct answers.
That feels like some hardcore X Y problem.
How do I add a new feature to Chromium, submit a pull request to Google, get it past their various layers of checks and policies, and mandate that all schools use this new option?