- From: Charles Pritchard <chuck@jumis.com>
- Date: Thu, 14 Jul 2011 21:22:44 -0700
- To: Alan Gresley <alan@css-class.com>
- Cc: "robert@ocallahan.org" <robert@ocallahan.org>, "Tab Atkins Jr." <jackalmage@gmail.com>, www-style list <www-style@w3.org>
I'd like to see cross-origin issues resolved in the hope of pointer-events: opacity(threshhold) and wrap-image proposals moving forward.
On Jul 14, 2011, at 9:12 PM, Alan Gresley <alan@css-class.com> wrote:
> On 15/07/2011 12:12 PM, Robert O'Callahan wrote:
>> Actually there is a problem, which is that external resource document loads
>> and image loads are different beasts right now and are implemented somewhat
>> differently in Gecko, and it would be a lot of work to determine if they can
>> be made perfectly consistent. One issue is that we impose a same-origin
>> restriction on SVG external resource loads, but not CSS image loads
>> obviously.
>>
>> Maybe we can get away with saying that url() with a fragment reference is an
>> external resource document load, and url() without a fragment reference is
>> an image load.
>>
>> Rob
>
>
> What about element(). Does it have same-origin restrictions?
>
> Evil document has this CSS and HTML.
>
>
> div {
> background: element(http://goodbank.com/foo.html#header);
> }
>
> button, input {
> color: transparent;
> background: transparent;
> border-color: transparent;
> position: /* where appropriate */
> }
>
> <div>
> <input />
> <input />
> <button />
> ......
> <div>
>
>
>
>
> --
> Alan Gresley
> http://css-3d.org/
> http://css-class.com/
>
Received on Friday, 15 July 2011 04:23:23 UTC