Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

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?


From 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});


Actually that alone won't work in a Chrome extension because of isolated worlds. You have to do a bit more gymnastics.


A really simple fix for this in Chrome is to type "javascript: delete console" into the omnibox. This will bring back the built-in console.


That seems like overkill. Just write an extension to unblock the console.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: