5 ms·
Guess it's time to recompile the browser (Chromium in this case?) with some extra switches to remove that chunk of JS code before it's executed?
by BadassFractal 13y ago
Guess it's time to recompile the browser (Chromium in this case?) with some extra switches to remove that chunk of JS code before it's executed?
- gizmo686 13y agoThat seems like overkill. Just write an extension to unblock the console.
- arg01 13y agoFrom the article: // But if you're feeling up to it, you can run the following line via an extension to prevent // this abuse: // Object.defineProperty(window, 'console', {configurable: false, value: window.console});
- aboodman 13y agoActually that alone won't work in a Chrome extension because of isolated worlds. You have to do a bit more gymnastics.
- deleted 13y ago[deleted]
- redbmk 13y agoA really simple fix for this in Chrome is to type "javascript: delete console" into the omnibox. This will bring back the built-in console.