On Thu, Nov 22, 2012 at 2:15 PM, Ian Hickson wrote:
> What do you think would be a good UI? Does something that would allow
> selecting a date/time in the current user's TZ and then have the
> information sent to the server in UTC would be a good UI?
That would probably be a reasonable fir
The "Paragraphs" section (3.2.5.3) gives an interesting example where
paragraphs can overlap when using an element, like , that defines
fallback content. To avoid the confusion of mixing the fallback paragraphs
with the sentences of the surrounding paragraph in the case where the
object resource is
On Wed, 5 Dec 2012, Anne van Kesteren wrote:
>
> Ian, for HTML that would allow easily dealing with the load exception on
> Window too.
The load exception is weirder than that. It's target is different than the
element that ever gets the event. Unless you mean the other exception, in
which cas
(It seems I somehow managed to not send this to the list the first
time around. Addendum included.)
On Tue, Dec 4, 2012 at 2:40 AM, Adam Barth wrote:
> On Mon, Dec 3, 2012 at 12:39 PM, Julian Reschke wrote:
>> On 2012-11-29 20:25, Adam Barth wrote:
>>> These are supported in Chrome. That's what
On Wed, 5 Dec 2012, Ed Summers wrote:
>
> Was the "id" itemprop you used in your examples a hypothetical property
> that would need to be defined at schema.org or elsewhere, or did you
> find it defined already?
Hypothetical. In the schema.org vocabulary, the existing "url" property
could be u
Ian,
Thanks very much for the guidance re: using and . I like
both solutions quite a bit better than leaning more on itemid for this
use case.
Was the "id" itemprop you used in your examples a hypothetical
property that would need to be defined at schema.org or elsewhere, or
did you find it defi
On Wed, Dec 5, 2012 at 4:38 PM, Dimitri Glazkov wrote:
> Yes, the intent is that in the the events from nodes, distributed to
> insertion points should feel as if there wasn't any shadow tree around them.
Right, but if is inside the shadow tree (rather than distributed
into it), you do not want
On Wed, 5 Dec 2012, Victor Costan wrote:
>
> There was a thread on this mailing list discussing making it possible to
> set the file data behind an element.
> http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2012-May/thread.html#36140
>
> The thread seems to have died down due to insufficie
On Wed, 5 Dec 2012, Jonas Sicking wrote:
> >>
> >> It seems to me like the best solution is to have a new HTTP header,
> >> with the four following values being allowed:
> >>
> >>Seamless-Options: allow-shrink-wrap
> >>Seamless-Options: allow-styling
> >>Seamless-Options: allow-shrink-
On Wed, Dec 5, 2012 at 3:49 AM, Anne van Kesteren wrote:
> On Wed, Dec 5, 2012 at 12:37 PM, Hayato Ito wrote:
> > Some kinds of events should be always stopped at the shadow boundaries.
> > See
> http://dvcs.w3.org/hg/webcomponents/raw-file/tip/spec/shadow/index.html#events-that-are-always-stopp
Dear WHATWG,
There was a thread on this mailing list discussing making it possible to
set the file data behind an element.
http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2012-May/thread.html#36140
The thread seems to have died down due to insufficient applications for the
proposal. I would
Am 05.12.2012 10:45 schrieb Jonas Sicking:
I hear no end of people arguing that HTTP headers are too hard for
people to use. Could we make these settable through elements as
well as, or instead of, using headers.
I am one of those authors with limited technical background. IMHO the
crucial po
On Wed, Dec 5, 2012 at 12:37 PM, Hayato Ito wrote:
> Some kinds of events should be always stopped at the shadow boundaries.
> See
> http://dvcs.w3.org/hg/webcomponents/raw-file/tip/spec/shadow/index.html#events-that-are-always-stopped
It's not entirely clear to me what that means. If an ends u
On Wed, Dec 5, 2012 at 8:16 PM, Anne van Kesteren wrote:
> On Wed, Dec 5, 2012 at 11:54 AM, Hayato Ito wrote:
>> Shadow DOM's event retargeting in WebKit uses one Event object for
>> every shadow trees.
>> When crossing shadow boundaries, an Event object's target (or
>> relatedTarget) is set to t
On Wed, Dec 5, 2012 at 11:54 AM, Hayato Ito wrote:
> Shadow DOM's event retargeting in WebKit uses one Event object for
> every shadow trees.
> When crossing shadow boundaries, an Event object's target (or
> relatedTarget) is set to the appropriate one, but the event object
> itself is reused.
In
Shadow DOM's event retargeting in WebKit uses one Event object for
every shadow trees.
When crossing shadow boundaries, an Event object's target (or
relatedTarget) is set to the appropriate one, but the event object
itself is reused.
FYI.
I've tried to implement event retargeting for seamless ifra
On Wed, Dec 5, 2012 at 1:02 AM, Ian Hickson wrote:
> I've done the HTML side of this (a paragraph), but the heavy lifting for
> this will be in DOM. Anne and I spoke about this earlier in #whatwg if you
> want to see the discussions. Some pointers to the logs can be found in the
> relevant DOM bug
On Mon, Dec 3, 2012 at 9:57 AM, Adam Barth wrote:
> On Fri, Nov 30, 2012 at 6:57 PM, Ian Hickson wrote:
>> On Sat, 26 May 2012, Adam Barth wrote:
>>>
>>> [CSP]
>>
>> CSP doesn't seem to include any features that would let you limit who is
>> allowed to iframe you, so I don't think CSP as designed
18 matches
Mail list logo
