On Jan 13, 2008, at 4:22 AM, Philip Taylor wrote:
What examples of information leakage is this change meant to prevent?
If you have an ImageData object then you can create a new object {
width: imgdata.width, height: imgdata.height, data: ...copy each array
element... } and then draw it,
On 13/01/2008, Oliver Hunt [EMAIL PROTECTED] wrote:
Writing to a canvas from a different origin isn't considered a threat,
the problem is
evil.example.com reading data from the canvas after naive.example.com
has put
private/confidential information into the canvas.
In that case,
On 13/01/2008, Oliver Hunt [EMAIL PROTECTED] wrote:
I did wonder about why other origins could read anything myself, so
you're not
alone -- it just seemed especially odd to allow images to be written
safely but not
ImageData.
As far as I'm aware, different origins can never read and write
Ah ha, i see i have misinterpreted that section, apologies for wasting
peoples time.
--Oliver
On Jan 13, 2008, at 5:33 AM, Philip Taylor wrote:
On 13/01/2008, Oliver Hunt [EMAIL PROTECTED] wrote:
I did wonder about why other origins could read anything myself, so
you're not
alone -- it
Ian Hickson skrev:
I considered all the feedback on having a number element (or
similar), quoted below.
While I think there is certainly something to be said for the
proposal, I don't think there is enough evidence that authors really
want or need this. I think we should focus on having
