News for hackers. Stuff that matters.
Re:Clipboard Hijacking with HTML5 in Chrome by userbinator on Thursday May 21, 2015 @11:52AM (#9583507)
This needs to be a thing (global, and also per-site):

    [ ] Allow reading clipboard content
    [ ] Allow writing clipboard content
I much prefer the "if there's an API that websites could abuse, there needs to be a setting to disable it" line of thought when it comes to browser functionality. I know it could result in many options (how about organising them better), and cause some to oppose with "but it'll be too hard/confusing for the users!", but this is how you empower your users to take control of their browsing experience - with fine-grained controls, not only large categories, and certainly not "it can't be changed from the UI".
Re:Clipboard Hijacking with HTML5 in Chrome by zimbatm on Thursday May 21, 2015 @04:06PM (#9585103)
> Allow reading clipboard content

This should never be a thing. The amount of snooping that's possible is incredibly high and people don't realize that kind of thing.

Re:Clipboard Hijacking with HTML5 in Chrome by bikeshack on Thursday May 21, 2015 @02:41PM (#9584597)
"Allow reading clipboard content"

As in something similar to how clipboard contents can be gleaned in iOS by a simple API call? I always wondered how many apps were abusing that iOS (feature?) and posting it to a collection server.

Re:Clipboard Hijacking with HTML5 in Chrome by TheLoneWolfling on Thursday May 21, 2015 @03:23PM (#9584876)
This is something I wished browsers would do in general.