View source blocks

[olegl]

Just recently, commit e72fc9b64116bf259e516096fcc60b58ae8ae1b3 dropped on Chromium sources, disallowing the "view source" in browser, if the website requests it to do so. There is no backlash at Google, but elsewhere though.

What is your position on this? I'd, personally, rather not have this patch in ungoogled-chromium. (And also not the devtools block.)

[kramred]

I doubt there are many places where ungoogled chromium is installed on Windows with this enterprise policy enabled.
If you know any examples or you can think of a scenario why ungoogled chromium should not honour that enterprise policy please elaborate.

So that would be Windows (Active Directory) clients where the admin set that policy and also installed ungoogled chomium – in the linked blog post they talk about preventing students on a school computer from using view source.

Now you want ungoogled chomium not to follow the policy that the admin set who also made ungoogled chromium available?

• If I was that admin I would compile ungoogled chromium without such a patch so that it to behaves as I configured it.
• If I was a student I would be mad that they have to resort to such cheap tricks to prevent me from looking at the source code of the page (and pity the the developer who could not think of a better way than storing the answers or whatever in the page source)

My personal position on this is that there's nothing to do here right now.

See also Objectives and Motivation and Philosophy