>> <http://dev.w3.org/2006/webapi/clipops/clipops.html> > Please forgive my ignorance. But I don't see a requirement that data > egressed from the local machine to be protected with SSL/TLS.
I can certainly add a note *encouraging* encryption, but it's not something we can "require" in a meaningful sense - it's several layers away from the parts of the process the spec is about. > Also, if the origin uses a secure scheme like HTTPS, then shouldn't > the script's also require the same? That is, shouldn't the spec avoid > fetching from https://www.example.com and then shipping clipboard data > off to http://www.ads.com? As an end user, I would go absolutely nuts if a computer was behaving inconsistently in apparently random ways like that. I'm pretty sure that no matter how security conscious you are, you probably copy and paste data between HTTPS and HTTP pages several times every month.. Having the browser block that because it pretends to know that some random data is important when I know it's not doesn't sound user friendly at all. -Hallvord
