On Mon, 21 May 2007 12:02:54 +0200, Anne van Kesteren <[EMAIL PROTECTED]>
wrote:
Internet Explorer 7 and Opera 9 don't move and to the
element during parsing (much like they don't do that for
On Mon, 21 May 2007 12:14:51 +0200, Maciej Stachowiak <[EMAIL PROTECTED]>
wrote:
If we simply ignore there's no longer a need to append elements
to the head element pointer. In fact, we can remove it. I'm not sure
how much this would complicate conformance checking, but it would
certainly
e
only possible value (indicating the input field or textarea should be
cleared upon focusing it) would probably be most suitable.
WebKit implements a placeholder= attribute which seems more suitable for
this purpose.
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
sheets. Anything that ends
up with a status code of 200 that is fetched from a "style sheet loader"
(, @import) is parsed and applied.
It would be nice if the specification said something along those lines.
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
ore general argument against
Content-Type.
At 10:44 +0200 UTC, on 2007-05-22, Anne van Kesteren wrote:
For compatibility with the web it seems important to simply ignore
Content-Type in all modes.
I'm confused about "in all modes" in this context. I thouht the idea was
to do
documents to match
reality. Until that happens HTML 5 provides the necessary details.
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
e not really up for
debate. It has to be compatible with the web.
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
iirc.
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
sers can start to comply
with their specification. That doesn't give us anything useful now so I
rather waste not too much time on it.
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
On Thu, 24 May 2007 19:07:58 +0200, Sander Tekelenburg <[EMAIL PROTECTED]>
wrote:
At 10:02 +0200 UTC, on 2007-05-23, Anne van Kesteren wrote:
On Wed, 23 May 2007 04:05:26 +0200, Sander Tekelenburg <[EMAIL PROTECTED]>
wrote:
I'm confused about "in all modes" in this
On Mon, 28 May 2007 08:21:58 +0200, Karl Dubost <[EMAIL PROTECTED]> wrote:
Le 24 mai 2007 à 16:50, Anne van Kesteren a écrit :
The HTML WG accepted to review the HTML 5 proposal. Presumably members
of the HTML WG are doing that. I'm not sure why they would need
tutorials as well t
rresponding
windows-* family decoder?)
1. I heard rumors that browsers treat that particular range special in
Unicode as well.
2. Maybe we should e-mail the charmod people about the bug in their
document?
Cheers,
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
han in
standards-mode.)
I don't care much for the semantic side of things but changing section 8.2
(and Acid2) to make not become as per HTML4
would be fine with me. We discussed this recently in #whatwg. Simon has
some ideas about it.
--
Anne van Kesteren
<http://annevankeste
On Wed, 30 May 2007 00:11:22 +0200, David Hyatt <[EMAIL PROTECTED]> wrote:
WinIE allows it, and we just changed WebKit to allow it too.
So what exactly do you do when scripting is _disabled_ in this case? For
instance with or ?
--
Anne van Kesteren
<http://annevankesteren.n
On Wed, 30 May 2007 10:23:51 +0200, Ivo Emanuel Gonçalves
<[EMAIL PROTECTED]> wrote:
As Anne pointed out, is used to display alternative content
that
you're making the assumption that any consumer of HTML content is
a browser.
I think the primary consumer is. Content is written mostly against
browsers, not parsing libraries. Parsing libraries should just follow the
specification (like html5lib tries to do).
--
Anne van Kes
content in both
languages. Compound documents where both the HTML and the SVG have a
title are possible, but that seems obscure enough that a special DOM API
to get both titles is probably unnecessary.
Even in that case only one title can be the document title.
--
Anne va
tainty they don't need to be reordered.
This is not an option. Consider
test
versus
test
Sending mutation events is probably the only way to go.
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
re are a lot of pages on the internet.
It might be something we could restrict to quirks mode pages though,
that's not a bad idea at all.
Please don't introduce more quirks mode nonsense. We have more than enough
already as it is.
--
Anne van Kesteren
<http://annevan
* tabindex -> tabIndex
* contenteditable -> contentEditable
* The irrelevant DOM attribute currently doesn't link because
there's no around its definition.
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
For .innerHTML = null Opera and Internet Explorer act as if the literal
string "null" was used. Firefox acts as if "" was used.
For .innerHTML = undefined Opera, Firefox and Internet Explorer act as if
the literal string "undefined" was used.
o if people code towards the new IE7.
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
d.
This attribute is defined in a way that is compatible with existing
implementations. It was introduced long ago but never formally specified.
So we can't really change it.
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
of its specs may not be changed
anymore, even though the HTML5 specs are still in working draft.
Correct. The specification is driven by implementation and vice versa.
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
These should be converted to LF too. One thing that might be interesting
to look into is the handling of LFCR in browsers (as opposed to CRLF). I
haven't done that yet... Some browsers (just tested Opera) also normalize
two newline entities following each other (CRLF pair).
--
Ann
's much more convenient to have event listeners in the markup. It also
makes sense if it's just a part of the application.
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
7;re wrong. maxlength= was made to truncate (again) because not
doing so broke existing content. (Implementation experience coming from
Opera implementing the Web Forms 2 specification.)
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
On Thu, 07 Jun 2007 23:12:38 +0200, Michael A. Puls II
<[EMAIL PROTECTED]> wrote:
On 6/7/07, Anne van Kesteren <[EMAIL PROTECTED]> wrote:
These should be converted to LF too. One thing that might be interesting
to look into is the handling of LFCR in browsers (as opposed to CRLF
s and the
root element can be beneficial for the readability of the final output.
I'd keep them there, just like XML does.
I don't think XML does that, actually.
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
On Sat, 09 Jun 2007 23:03:54 +0200, Michel Fortin
<[EMAIL PROTECTED]> wrote:
I don't think XML does that, actually.
See the first paragraph of http://www.w3.org/TR/xml/#syntax for the reason
why this is so. White space outside the the root element is markup and not
text.
29%5B0%5D.firstChild.data%20%3D%20%22x%5Cr%5Cnx%22%20%3C/script%3E%3C/pre%3E%0D%0A
can be used for playing with this.
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
ne at some point. Well, at least
the version switches that are important for interoparability.
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
thors may start using
in combination with display:none which is not what is desired.
(This was mentioned on IRC, but it's probably worth mentioning here as
well.)
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
for tokenization differences I suppose, but I don't believe you're testing
those here and I think there's still some research to be done for the
exact tokenization rules.
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
On Wed, 13 Jun 2007 10:26:48 +0200, Thomas Broyer <[EMAIL PROTECTED]>
wrote:
2007/6/13, Simon Pieters:
On Wed, 13 Jun 2007 09:11:31 +0200, Thomas Broyer wrote:
> I'd rather change the #tokenisation section to generate more parse
> errors.
Why? What if you want to pass a paramater to a plugin w
the particular plugin implementation.
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
e able to use it with and be forced to use
. Given that is deprecated, that's not a big deal.
is not deprecated. It's the dedicated element for plugin content.
In fact, no element or attribute is deprecated in HTML5. They are either
part of the language or not.
mbed" means "display" and
"object" means "run" but breaking the fixed interface rule weighs more
than
introducing this distinction IMHO.
How does deprecating help with your specific problem?
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
We're
encountering some difficulties with the current algorithm.
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
hings like "naïve"
actually conforming. I don't know if we want this.
Rather not. This would break unencoded URLs:
?foo=bar®ion=baz → ?foo=bar®ion=baz
You mean that Internet Explorer breaks them already? That doesn't make
much sense to me.
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
For what it's worth, they have _always_ been optional in HTML. And you're
right, some people might do that. In fact, it was done wrong so often for
that browsers now all support a charset= attribute on for
indicating the document encoding.
--
Anne van Kesteren
<
On Fri, 15 Jun 2007 21:21:06 +0200, Kornel Lesinski <[EMAIL PROTECTED]>
wrote:
On Fri, 15 Jun 2007 19:37:46 +0100, Anne van Kesteren <[EMAIL PROTECTED]>
wrote:
I've defined the parsing and conformance requirements in a way that
matches IE. As a side-effect, this has made t
t from &, ", ', etc.? The element eventually
created would be non-conforming anyway.
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
ibute values as
errors.
Neh: http://www.whatwg.org/>WHATWG. Maybe a warning
at the discretion of conformance checkers.
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
"DOCTYPE name state" and "After DOCTYPE name state" should probably set
the correctness flag to incorrect for EOF.
For the tree construction phase a correctness flag that is set to
incorrect should also be a parse error. Otherwise foobarnonsense> will be conforming.
On Mon, 18 Jun 2007 16:26:10 +0200, Anne van Kesteren <[EMAIL PROTECTED]>
wrote:
For the tree construction phase a correctness flag that is set to
incorrect should also be a parse error. Otherwise foobarnonsense> will be conforming.
This is flagged at the tokenizing level. S
On Mon, 18 Jun 2007 22:25:46 +0200, Ian Hickson <[EMAIL PROTECTED]> wrote:
On Sun, 10 Dec 2006, Anne van Kesteren wrote:
The "Anything else" case should probably trigger a parse error before
reprocessing the current token.
Why? Could you show a sample of markup that would go t
On Wed, 20 Jun 2007 04:00:03 +0200, Ian Hickson <[EMAIL PROTECTED]> wrote:
On Mon, 21 May 2007, Anne van Kesteren wrote:
Internet Explorer 7 and Opera 9 don't move and to the
element during parsing (much like they don't do that for
iven that conformance checkers are required to
follow the parsing section this is a problem I think.
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
On Mon, 18 Jun 2007 22:26:57 +0200, Ian Hickson <[EMAIL PROTECTED]> wrote:
On Sat, 9 Dec 2006, Anne van Kesteren wrote:
On Fri, 08 Dec 2006 22:57:07 +0100, Ian Hickson <[EMAIL PROTECTED]> wrote:
The section "If the child node is a Text or CDATASection node"
should inclu
I'm not convinced
http://html5.org/tools/web-apps-tracker?from=917&to=918
is a good change to make. This changes how things like or
If you encounter a start tag, end tag, end-of-file or non-space character
token during the initial phase that token should be reprocessed in the
root element phase. Just switching to the root element phase is not enough.
--
Anne van Kesteren
<http://annevankesteren.nl/>
On Wed, 20 Jun 2007 22:17:26 +0200, Ian Hickson <[EMAIL PROTECTED]> wrote:
On Wed, 20 Jun 2007, Anne van Kesteren wrote:
I'm not convinced
http://html5.org/tools/web-apps-tracker?from=917&to=918
is a good change to make. This changes how things like or
.
Something like application/x-dom-document-event-stream...
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
Currently if you encounter or inside a element
in the scripting disabled case you will get incorrect results as the
current node is not the element but the element.
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
rror
handling.)
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
On Thu, 21 Jun 2007 17:13:40 +0200, Thomas Broyer <[EMAIL PROTECTED]>
wrote:
2007/6/21, Anne van Kesteren:
It would be good if radio controls can not be shared accross multiple
forms as that makes them a huge mess. Opera's proposal would be that if
there's a form attribute sp
On Fri, 22 Jun 2007 07:08:17 +0200, Ian Hickson <[EMAIL PROTECTED]> wrote:
On Wed, 20 Jun 2007, Anne van Kesteren wrote:
If you encounter a start tag, end tag, end-of-file or non-space
character token during the initial phase that token should be
reprocessed in the root element phase
On Fri, 22 Jun 2007 13:43:17 +0200, Anne van Kesteren <[EMAIL PROTECTED]>
wrote:
On Fri, 22 Jun 2007 07:08:17 +0200, Ian Hickson <[EMAIL PROTECTED]> wrote:
On Wed, 20 Jun 2007, Anne van Kesteren wrote:
If you encounter a start tag, end tag, end-of-file or non-space
character toke
eah, it makes sense to follow Internet Explorer 7 for this.
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
These closing tags also need to be "guided" through the head element phase
and such to ensure documents such as
behave similar to the browsers we try to imitate in English.
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
icated rules
that do not
actually handle existing documents optimally.
1) It was quite easy to implement. Took me about thirty minutes including
updating
several tests and adding a few extra tests. (In html5lib, Python.)
2) You're saying that content breaks in IE?
--
Anne van Kes
most browsers (not sure about mobile devices though).
*
*
*
... cover this.
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
issues we have with today
(although, like CSS, it's still usable).
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
graphics primitives to handle any rectangular entities, not just
?
There are lots of potential problems, such as how it would interact with
plugins or some video if both render to the same context. Or if you allow
it on elements such as what would happen if text resizing caused the
canvas
's no such event handler on the Audio object.
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
ich takes into account the tag.
Yes, but window.location.href does not. It probably makes sense to make it
work exactly like:
var i = new Image()
i.src = url
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
hor. I can't really
think of any use cases at the moment though.
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
be to make
certain parts of the image not "clickable". Given that, it makes sense to
me to reduce the number of attributes browsers have to implement for
...
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
Wouldn't it make sense to dispatch the event whenever location.hash
changes value? When following a link for instance? (Unless I misunderstood
something it's currently only dispatched in history traversal.)
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
't use getElementById()
anyway as you have to check both id= and name=. To keep behavior the same
between HTML quirks, HTML standards and XML doing a case-insensitive match
makes some sense.
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
document.writeln() without arguments should cause a single line-break to
be inserted into the stream. This should probably be part of the
document.writeln() definition.
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
s "no longer" very
relevant.)
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
On Thu, 13 Sep 2007 17:30:02 +0200, Aaron Boodman <[EMAIL PROTECTED]> wrote:
On Sep 13, 2007 4:44 AM, Anne van Kesteren <[EMAIL PROTECTED]> wrote:
I feel like me and the other querystringers are missing some critical
detail that would make omitting querystring support work. So here
rry about the
browser/scripting context change.
You seem to have missed what I pointed out earlier:
http://www.whatwg.org/specs/web-apps/current-work/#pushstate This allows
applications to make distinct URIs while keeping all the other benefits.
--
Anne van Kesteren
<http://an
abase that is not available for some reason
* Database that is full
I think it should also be a bit more clear on how the user agent
constructs the SQL statement.
Cheers,
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
for this.
XMLHttpRequest level 2 supports sending ByteArray. So you could do
something like the following maybe:
xhr.send(file.bytes)
Although if HTML5 gains a native File object I suppose support for that
could be added as well if there's any benefit.
--
Anne van Kesteren
<
Quoting Rikkert Koppes <[EMAIL PROTECTED]>:
> [...] A
> disabled control can still match this pseudo-class; the states are
> orthogonal.
>
> I believe the term "orthogonal" is incorrect here.
:read-write is orthogonal to :disabled. That's co
to be
decided for Infinity -Infinity and NaN for all of those. I don't have a
strong opinion on it either way, although I would prefer it to be decided
quickly so we have some time to propagate the changes in time for Opera
9.5.
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
On Tue, 19 Dec 2006 17:18:48 +0100, Anne van Kesteren <[EMAIL PROTECTED]>
wrote:
The draft should probably be more explicit about:
Assuming "form1" and "form2" both exist selecting the first control will
unset the controls associated with
should be
possible for the browser to layer something div-equivalent over the
media elements supporting captioning and pipe the HTML captions into it
(with caution, imagine a caption itself recursively embedding a video).
I think the cue points feature is designed to do that.
--
Anne van Kesteren
some platforms there's not much storage space available and knowing
whether or not there's some space left is useful. So you can decide to
only store the critical data for instance.
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
at matches what Opera implements, too.
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
On Fri, 19 Oct 2007 12:02:24 +0200, timeless <[EMAIL PROTECTED]> wrote:
On 10/19/07, Anne van Kesteren <[EMAIL PROTECTED]> wrote:
For that you need something in the browser UI. There's a large, maybe
infinite, number of ways to make not visible even if it's within
the
On Fri, 19 Oct 2007 12:36:17 +0200, Robert O'Callahan
<[EMAIL PROTECTED]> wrote:
On Oct 19, 2007 9:03 PM, Anne van Kesteren <[EMAIL PROTECTED]> wrote:
var soundeffect = new Audio("sound.wav")
soundeffect.onload = function() { this.play() }
which is what was poss
e; left:-1000px }
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
) { this.play() }
which is what was possible with the old Audio API (became ) Opera
implemented.
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
ker?from=1093&to=1094
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
nicer at some point.
Cheers,
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
g that that have an explicit "null" though. Who do other
people think?
There at least some feedback from the developer community that they'd like
to see optional arguments:
http://www.dustindiaz.com/dom-interfaces-suck/
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
ink that's one of the reasons it's simply gets clipped instead of
scaled. (And clipping is a feature too, keep that in mind.)
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
The way newlines are handled for should also apply to
to keep things consistent. That is, lines are CRLF
delimited.
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
orrect the spelling of "referer", we certainly need
not duplicate it for "noreferrer". There must be some end to this
self-humiliation.
I think it's way better to stay consistent. Especially as the feature
affects the Referer (sic) header.
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
more off-topic, there are people working on solving this
issue: http://lists.w3.org/Archives/Public/www-style/2007May/0030.html
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
e know what happened with this?
"Regardless of any specific issues that may exist with the draft itself,
there was zero interest demonstrated. So, now it really is dead."
-- http://www.imc.org/atom-syntax/mail-archive/msg19733.html
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
what I consider misuse of in that example, I would
encourage people to use hCard to mark up a name instead of us introducing
an element for the purpose.
How would you mark that up instead? (currently) doesn't allow
block-level descendents.
--
Anne van Kesteren
<http://annevankeste
napping.
The CSS WG is working on this:
http://dev.w3.org/csswg/cssom-view/
Discussion "should" take place on [EMAIL PROTECTED] The draft will be
published as a W3C First Public Working Draft soonish, though this may be
after new year given the holidays and such.
--
Anne van
On Fri, 28 Dec 2007 18:13:38 +0100, Christian Schmidt <[EMAIL PROTECTED]>
wrote:
What do you think of this?
I think that globalStorage and sessionStorage obviate the need for cookies.
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
velopers more likely to use it.
This does have the disadvantage that you always share your data with
everyone where you can restrict that with Access Control. Especially for
authenticated services this might be problematic.
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
URL() and getImageData() functions throw for an unsafe
HTMLCanvasElement.
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
501 - 600 of 1841 matches
Mail list logo
