On Sat, 15 Aug 2009 08:47:32 +0200, Jonas Sicking wrote:
> The problem is that you can't use fragment identifiers with data-URIs.
>
> For example
>
> data:text/plain,hello world#frag
>
> Represents a text/plain document with the contents:
>
> hello world#frag
>
> It does not represent the 'frag' p
On Fri, Aug 14, 2009 at 4:08 AM, Philip Jägenstedt wrote:
> On Fri, 14 Aug 2009 12:48:59 +0200, Silvia Pfeiffer
> wrote:
>
>> On Fri, Aug 14, 2009 at 7:54 PM, Dr. Markus Walther
>> wrote:
>>>
>>>
>>> Silvia Pfeiffer wrote:
2009/8/14 Dr. Markus Walther :
>
> Hi,
>
>> The .
On Fri, Aug 14, 2009 at 12:02 PM, Jonas Sicking wrote:
> On Fri, Aug 14, 2009 at 3:35 AM, Ian Hickson wrote:
>> On Fri, 7 Aug 2009, Jonas Sicking wrote:
>>> >
>>> > I haven't removed HTMLCollection.tags yet, since it appears to be
>>> > implemented by most browsers. If we can get Opera and WebKit t
On Mon, 10 Aug 2009, Chris Cressman wrote:
>
> >From section 1.9:
>
> "Each element in the DOM tree is represented by an object, and these
> objects have APIs so that they can be manipulated. For instance, a
> link (e.g. the a element in the tree above) can have its "href"
> attributed changed in
On Fri, Aug 14, 2009 at 4:06 PM, Ian Hickson wrote:
>
> On Sun, 9 Aug 2009, Jeremy Orlow wrote:
> >
> > I feel like redirects add unnecessary complexity.
> >
> > We're already asking application developers to handle ACKing, keep
> > alives, multi-plexing, connection limiting, authentication, etc
>
On Sat, 8 Aug 2009, Adam Barth wrote:
>
> [[
> Send the string "WebSocket-Origin" followed by a U+003A COLON (":")
> followed by the ASCII serialization of the origin from which the
> server is willing to accept connections, followed by a CRLF pair
> (0x0d 0x0a).
>
>For instance:
>
>
On Sat, 8 Aug 2009, Adam Barth wrote:
>
> In fact, the situation is worse than the above because the websocket
> protocol supports cookies. Instead of relying on a firewall and IP
> authentication, the victim server could be on the public Internet and be
> relying upon cookie authentication.
>
On Fri, Aug 14, 2009 at 11:48 AM, Cready, James wrote:
> Except of course for the following:
>and
>
> And these "obsolete elements" still supported by legacy UAs:
> and
Those are just unclosed, they're not self-closing. If you use the
"/>" syntax it's not closing the tag, it's ju
I'm sorry - we cannot say anything about our plans at this point.
Thanks,
Jeremy
On Mon, Aug 10, 2009 at 5:30 PM, Nils Dagsson
Moskopp wrote:
> Am Dienstag, den 11.08.2009, 00:44 +0100 schrieb Sam Kuper:
>> In recent news, Google may be about to open source On2 codecs, perhaps
>> creating a route
On Fri, Aug 14, 2009 at 3:45 AM, Ian Hickson wrote:
> On Fri, 7 Aug 2009, Jonas Sicking wrote:
>> I agree that these are very interesting features. Especially connection
>> multiplexing is something that I think is a good idea, for the reasons
>> you've mentioned elsewhere in this thread (multiple
Tab,
your response is off-topic, if it's not related to forms in SVG
ie off-topic for this email, rather than the lists..
cheers
~:"
On 14 Aug 2009, at 15:07, Tab Atkins Jr. wrote:
2009/8/14 "~:'' ありがとうございました"
:
A plan to enable Forms?
Does the SVG WG have a plan to enable Forms?
what is
On Fri, Aug 14, 2009 at 12:35 PM, João Eiras wrote:
> From an implementor's point of view it is much harder to implement and keep
> up with a mutating specification. During implementation a stable spec is
> preferred.
>
As a browser implementer, I have certainly not found the dynamic nature of
t
Hi,
Versioning is a larger topic recently:
http://lists.w3.org/Archives/Public/public-webapps/2009AprJun/0655.html
http://lists.w3.org/Archives/Public/www-tag/2009Aug/0027.html
http://lists.w3.org/Archives/Public/www-tag/2009Aug/0029.html
I wonder whether there could be a consistent pattern throu
On Fri, 14 Aug 2009 12:01:31 +0100, Ian Hickson wrote:
On Sun, 9 Aug 2009, Aaron Boodman wrote:
I frequently see the comment on this list and in other forums that
something is "too late" for HTML5, and therefore discussion should be
deferred.
I would like to propose that we get rid of the co
On Fri, Aug 14, 2009 at 3:35 AM, Ian Hickson wrote:
> On Fri, 7 Aug 2009, Jonas Sicking wrote:
>> >
>> > I haven't removed HTMLCollection.tags yet, since it appears to be
>> > implemented by most browsers. If we can get Opera and WebKit to remove
>> > support, then I'll remove it from the spec.
>>
Currently, SharedWorkers accept both a "url" parameter and a "name"
parameter - the purpose is to let pages run multiple SharedWorkers using the
same script resource without having to load separate resources from the
server.
Per section 4.8.3 of the SharedWorkers spec, if a page loads a shared work
On Fri, Aug 14, 2009 at 3:45 AM, Ian Hickson wrote:
> On Fri, 7 Aug 2009, Jonas Sicking wrote:
> >
> > I agree that these are very interesting features. Especially connection
> > multiplexing is something that I think is a good idea, for the reasons
> > you've mentioned elsewhere in this thread (
>> No elements in text/html can be self-closing.
>
> Except of course for the following:
>and
>
> And these "obsolete elements" still supported by legacy UAs:
> and
Except, of course, that these are not self closing.
Regards,
Rimantas
--
http://rimantas.com/
On Fri, Aug 14, 2009 at 9:23 AM, Tab Atkins Jr. wrote:
> Of course, I'm stuck on 3.0.12 since 3.5 auto-crashes on load on my
> work computer. ;_;
For everyone concerned, it's been fixed now. It was a rogue DLL.
Thanks to LDB for pointing me to the correct KB article, and thanks to
Shaver and Lac
On Fri, Aug 14, 2009 at 10:48 AM, Cready, James wrote:
>> No elements in text/html can be self-closing.
>
> Except of course for the following:
>and
>
> And these "obsolete elements" still supported by legacy UAs:
> and
None of those are self-closing in the HTML syntax; they're al
> No elements in text/html can be self-closing.
Except of course for the following:
and
And these "obsolete elements" still supported by legacy UAs:
and
> Generally speaking I think we should avoid making the platform have too
> many redundant features, however illogical some of
On Fri, Aug 14, 2009 at 3:09 PM, Henri Sivonen wrote:
> On Aug 14, 2009, at 16:06, Silvia Pfeiffer wrote:
>
>> There is only one thing I can think about that an "alt" attribute
>> could provide that nothing else does: as a blind user tabs onto a
>> video element, the "alt" attribute's content could
On Fri, Aug 14, 2009 at 9:09 AM, Aryeh Gregor wrote:
> On Fri, Aug 14, 2009 at 10:02 AM, Tab Atkins Jr. wrote:
>> I can't load the full spec - it locks my browser - and I can't find
>> any relevant text at
>> http://www.whatwg.org/specs/web-apps/current-work/multipage/forms.html#the-textarea-elemen
On Fri, Aug 14, 2009 at 10:02 AM, Tab Atkins Jr. wrote:
> I can't load the full spec - it locks my browser - and I can't find
> any relevant text at
> http://www.whatwg.org/specs/web-apps/current-work/multipage/forms.html#the-textarea-element.
> Is there some other place I should be looking in the
2009/8/14 "~:'' ありがとうございました" :
> A plan to enable Forms?
>
> Does the SVG WG have a plan to enable Forms?
>
> what is the current status regarding sockets and SVG 1.2?
>
> regards
>
> ~:"
>
> The popular SVG-native web browsers such as Opera, Mozilla and Webkit have
> not implemented xforms.
>
> HT
On Fri, 14 Aug 2009 16:02:52 +0200, Tab Atkins Jr. wrote:
> Is there some other place I should be looking in the multipage spec?
http://www.whatwg.org/specs/web-apps/current-work/multipage/the-xhtml-syntax.html#the-textarea-element-0
--
Anne van Kesteren
http://annevankesteren.nl/
On Fri, Aug 14, 2009 at 4:22 AM, Ian Hickson wrote:
> On Fri, 7 Aug 2009, Tab Atkins Jr. wrote:
>>
>> Proposal
>>
>> Add the "off" state to the @wrap attribute for textareas.
>
> The "off" value is already defined in HTML5 for the purpose of rendering
> [1]. However, it isn't a conforming
On Fri, Aug 14, 2009 at 5:09 AM, Ian Hickson wrote:
> I wouldn't bother wrapping any of the above as small print. If you're
> structuring this enough that you have numbered lists and paragraphs and
> everything, then it's either not small print, or it shouldn't be.
To the contrary: the more text t
On Fri, Aug 14, 2009 at 11:09 PM, Henri Sivonen wrote:
> On Aug 14, 2009, at 16:06, Silvia Pfeiffer wrote:
>
>> There is only one thing I can think about that an "alt" attribute
>> could provide that nothing else does: as a blind user tabs onto a
>> video element, the "alt" attribute's content coul
On Aug 14, 2009, at 16:06, Silvia Pfeiffer wrote:
There is only one thing I can think about that an "alt" attribute
could provide that nothing else does: as a blind user tabs onto a
video element, the "alt" attribute's content could be read out and
briefly describe what is visible in the poster
On Fri, Aug 14, 2009 at 9:13 PM, Ian Hickson wrote:
> On Mon, 10 Aug 2009, Remco wrote:
>>
>> Shouldn't s and s (and maybe s too?) also have an
>> alt attribute? A quick Google search tells me this has not been
>> discussed before.
>
> For users who can use audio but not video, authors should eithe
On Mon, 10 Aug 2009, Remco wrote:
>
> Shouldn't s and s (and maybe s too?) also have an
> alt attribute? A quick Google search tells me this has not been
> discussed before.
For users who can use audio but not video, authors should either provide
audio descriptions in the video file as alternat
On Fri, 14 Aug 2009 12:48:59 +0200, Silvia Pfeiffer
wrote:
On Fri, Aug 14, 2009 at 7:54 PM, Dr. Markus Walther
wrote:
Silvia Pfeiffer wrote:
2009/8/14 Dr. Markus Walther :
Hi,
The .start/.end properties were dropped in favor of media fragments,
which the Media Fragments Working Group
On Fri, 14 Aug 2009 10:42:50 +0200, Dr. Markus Walther
wrote:
Silvia,
2009/8/13 Dr. Markus Walther :
please note that with cue ranges removed, the last HTML 5 method to
perform audio subinterval selection is gone.
Not quite. You can always use the video.currentTime property in a
javascri
On Sun, 9 Aug 2009, Aaron Boodman wrote:
>
> I frequently see the comment on this list and in other forums that
> something is "too late" for HTML5, and therefore discussion should be
> deferred.
>
> I would like to propose that we get rid of the concepts of "versions"
> altogether from HTML.
On Fri, 14 Aug 2009 10:28:14 +0200, Dr. Markus Walther
wrote:
Hi,
The .start/.end properties were dropped in favor of media fragments,
which the Media Fragments Working Group is producing a spec for.
Who decided this? Has this decision been made public on this list?
It happened in Novem
On Sat, 8 Aug 2009, Melvin Carvalho wrote:
>
> Since WebSockets seem to be talked about recently. I've have a couple
> of questions re: the http websocket implementation and https ie wss
I'm not sure what you mean by "the http websocket implementation", but I
will try to reply to your question
On Fri, Aug 14, 2009 at 7:54 PM, Dr. Markus Walther wrote:
>
>
> Silvia Pfeiffer wrote:
>> 2009/8/14 Dr. Markus Walther :
>>> Hi,
>>>
The .start/.end properties were dropped in favor of media fragments,
which the Media Fragments Working Group is producing a spec for.
>>> Who decided this?
On Fri, 7 Aug 2009, Jonas Sicking wrote:
>
> I agree that these are very interesting features. Especially connection
> multiplexing is something that I think is a good idea, for the reasons
> you've mentioned elsewhere in this thread (multiple widgets on the same
> page).
How do you envisage m
On Fri, 7 Aug 2009, Jonas Sicking wrote:
> >
> > I haven't removed HTMLCollection.tags yet, since it appears to be
> > implemented by most browsers. If we can get Opera and WebKit to remove
> > support, then I'll remove it from the spec.
>
> Given that we have some data indicating that .tags() i
On Thu, 13 Aug 2009 22:05:26 -0400, Ian Hickson wrote:
- Should s exist all the time whether they are attached to the
document or not?
Assuming you mean the plugins, as opposed to the elements themselves,
then
the way the spec is written, the plugin instantiates regardless of
whether
it is
Silvia Pfeiffer wrote:
> 2009/8/14 Dr. Markus Walther :
>> Hi,
>>
>>> The .start/.end properties were dropped in favor of media fragments,
>>> which the Media Fragments Working Group is producing a spec for.
>> Who decided this? Has this decision been made public on this list?
>>
>>> It will
>>>
>> - Should the type attribute take precedence over the Content-Type header?
>
> No, I believe what the spec says here is the preferred behaviour. Unless
> this is incompatible with legacy content, we should try to move towards
> this behaviour.
OK, should the spec mention the change that Boris
On Fri, 7 Aug 2009, Tab Atkins Jr. wrote:
>
> Proposal
>
> Add the "off" state to the @wrap attribute for textareas.
>
> Explanation
> ===
> The "off" state prevents a textarea from wrapping text at all while
> displaying. Instead, text that is too long for the textarea trigger a
2009/8/14 Dr. Markus Walther :
> Hi,
>
>> The .start/.end properties were dropped in favor of media fragments,
>> which the Media Fragments Working Group is producing a spec for.
>
> Who decided this? Has this decision been made public on this list?
>
>> It will
>> be something like http://www.exam
On Fri, 7 Aug 2009, Remy Sharp wrote:
>
> The HTML 5 spec says:
>
> "Small print typically features disclaimers, caveats, legal
> restrictions, or copyrights. Small print is also sometimes used for
> attribution, or for satisfying licensing requirements."
>
> So I'm making a list of disclaimer
Silvia,
> 2009/8/13 Dr. Markus Walther :
>> please note that with cue ranges removed, the last HTML 5 method to
>> perform audio subinterval selection is gone.
>
> Not quite. You can always use the video.currentTime property in a
> javascript to directly jump to a time offset in a video. And in y
Tab Atkins Jr. schrieb:
On Thu, Aug 6, 2009 at 6:14 PM, Cready, James wrote:
You make a great point. But whether or not you use the XML/XHTML
or the HTML 4 doesn¹t matter much. Since like I showed in my
previous example: the instant you specify a src attribute on your opening
tag the browser
Hi,
> The .start/.end properties were dropped in favor of media fragments,
> which the Media Fragments Working Group is producing a spec for.
Who decided this? Has this decision been made public on this list?
> It will
> be something like http://www.example.com/movie.mov#t=12.33,21.16
var audio
A plan to enable Forms?
Does the SVG WG have a plan to enable Forms?
what is the current status regarding sockets and SVG 1.2?
regards
~:"
The popular SVG-native web browsers such as Opera, Mozilla and Webkit
have not implemented xforms.
HTML5 proposal:
http://www.whatwg.org/specs/web-ap
50 matches
Mail list logo
