> so I doubt any blocking plugin works this way. That sounds like an assumption based on how you would implement it. Until Chrome implemented its native click

> so I doubt any blocking plugin works this way. That sounds like an assumption based on how you would implement it. Until Chrome implemented its native click to play, most of "click to play" plugins were targeted at advertising and simply blocked visual rendering and audio playback. It's not for lack of trying, the underlying framework for the plugin to stop execution simply didn't exist.