3 ms·
I see a lot of people bagging on Java but I think the real problem are the browsers. Java is the one being used in this attack but next time it could be Flash o
by guelo 14y ago
I see a lot of people bagging on Java but I think the real problem are the browsers. Java is the one being used in this attack but next time it could be Flash or Acrobat or any other plugin or even 3rd party Javascript scripts. The default behavior of browsers should be similar to flash-block, Ghosterly and other similar plugins: the plugin only runs when the user requests it by acknowledging the source and hitting a "play" button inside the page. No auto-loaded code should ever run.
- pcwalton 14y agoFirefox will soon be doing this, except for Flash.
- robert-wallis 14y agoChrome's "click to play" plugin setting chrome://settings/content has a nice user experience, because on YouTube you click the video that you want to play instead of clicking some off menu to enable Flash on the whole domain. I think that setting should be default, but likely the AdSense team would have a throwdown with the Chromium team if that happened.