3 ms·
Seems to be a useful feature also when you want to use Chromium as Kiosk software. I honestly don't get why so many commentators are upset. They are using Goog
by chromanoid 5y ago
Seems to be a useful feature also when you want to use Chromium as Kiosk software.
I honestly don't get why so many commentators are upset. They are using Google Forms for tests. And these tests leak answers through the source code. Schools are not well funded and this setup itself is not very professional. When you can fix this by giving admins such possibilities, why not?
It's not like your Chrome will prevent you from viewing any sources. As you can also read in the article the restriction can be limited to certain URLs. IT ONLY AFFECTS MANAGED ENVIRONMENTS WHERE ADMINS CAN DO MUCH MORE RESTRICITNG THINGS ANYWAY.
- watermelon0 5y agoSo much this. I think the issue is that the fix was packed up as the solution for broken test-taking software (or misuse of Google Forms for that intention), and people everywhere are complaining that it's not a valid reason, with which I agree. However, there are legit environments where people might want to prevent users from accessing devtools and view-source functionality, like when using it as a kiosk software. From security standpoint, it might be also reasonable to disable at least devtools in enterprise environments, since users can not necessarily be trusted with such access (which is the reason why many sites, such as Facebook, display warning to not enter anything in the console, especially if someone instructed them or they found it online).