com” but not to “view-source :https ://9to5google. For example, a company could block access to “https ://9to5google. In 2018, it was reported to Google via the Chromium Bug Tracker that one of Chrome Enterprise’s existing policies - a URL blocklist - was unable to block requests to “view-source:” addresses. These tools are especially useful for web developers (from absolute beginners to experts) to debug issues with their own sites or simply learn more about how their favorite sites were made. Or you can even get an interactive view of the page’s code using Chrome’s DevTools by pressing F12 or Ctrl-Shift-I. Your browser will then interpret and render that code into a proper webpage.Įven after all of that rendering work, you can still view the raw code of a page by pressing Ctrl-U (or right-clicking somewhere on the page and clicking “View page source”). Unless you use a school/company-owned Chromebook or use Chrome Enterprise, this enterprise policy will not directly affect you.Īs a quick and simple explanation, when you navigate to a website, your browser receives the page’s HTML, CSS, and JavaScript code from the server. This article discusses an enterprise policy, which can be thought of as an option available only to administrators of devices/accounts owned by a company or organization. To fix a longstanding bug that could view restricted URLs and sometimes reveal test answers, IT administrators will soon be able to block Google Chrome and Microsoft Edge from viewing the source code of webpages.īefore we dive into what this policy can do and whether or not it’s a good solution, one thing needs to be made clear up front.

Get chromium source code