immed from any other attributes
# (e.g. the value attribute).
Could you add a note that there is some form of normalization applied to these
attributes in XML documents as described here:
<http://www.w3.org/TR/REC-xml/#AVNormalize>. This could be helpful and would
prevent confusion.
Cheers,
Anne
--
Anne van Kesteren
<http://annevankesteren.nl/>
fore the value of an attribute is passed to the application
# or checked for validity, the XML processor MUST normalize the
# attribute value by applying the algorithm below
(Also, internal subsets are required to be supported by XML parsers.)
--
Anne van Kesteren
<http://annevankesteren.nl/>
Can this demo be fixed? The button named "add" needs to have a template
attribute with the literal value of "player".
Furthermore, the DOCTYPE should be changed to "".
Cheers,
Anne
--
Anne van Kesteren
<http://annevankesteren.nl/>
Could you please change the namespace to "http://n.whatwg.org/formdata";. Perhaps
you also want to note at http://n.whatwg.org/formdata that it can be used for
seeding the form with initial values as well.
Cheers,
Anne
--
Anne van Kesteren
<http://annevankesteren.nl/>
les authors should be aware about when dealing with forms.
This seemed
like the most appropriate place to add the note.
Cheers,
Anne
--
Anne van Kesteren
<http://annevankesteren.nl/>
be aware about when dealing with forms.
This seemed like the most appropriate place to add the note.
I don't see how these rules will affect users unless they go out of their
way to make DTDs, in which case they deserve whatever they get.
The normalization happens without DTDs.
--
Anne van Kesteren
<http://annevankesteren.nl/>
alisation
only occurs with DTDs.
In HTML I never had the problem that new lines were removed. There is quite a
substantial difference here imho.
--
Anne van Kesteren
<http://annevankesteren.nl/>
lly, some are more
compliant than others).
Right... You mean the one that is based on SGML?
--
Anne van Kesteren
<http://annevankesteren.nl/>
tml:script.)
Kind regards,
Anne
--
Anne van Kesteren
<http://annevankesteren.nl/>
Quoting Jim Ley <[EMAIL PROTECTED]>:
Is this not a bug? I can't see anywhere in any XHTML specification
that states that html:style children of html:style elements should be
treated as if they were stylesheets.
Error handling for the html:style element is not defined.
--
Anne v
. (But addressing fonts, line-height, etc. might be
difficult.)
Also, adding text support will bring to par with MSIE's VML.
Isn't VML substantially closer to SVG (which supports text)?
Yeah, I believe so, see <http://www.w3.org/TR/1998/NOTE-VML-19980513>.
--
A
even:
<http://annevankesteren.nl/test/cdf/cdi/007>
They are for different purposes though, last time I checked.
--
Anne van Kesteren
<http://annevankesteren.nl/>
r/blog/archives/000564.html
Yeah, that was my point from the beginning. I suffered from it myself as well.
--
Anne van Kesteren
<http://annevankesteren.nl/>
ports the CSS color value "orange"? You
don't.
Cheers,
Anne
--
Anne van Kesteren
<http://annevankesteren.nl/>
ature "XHTML" with version string "2.0" is already taken, see:
<http://www.w3.org/TR/DOM-Level-2-HTML/html.html#ID-1176245063>
Cheers,
Anne
--
Anne van Kesteren
<http://annevankesteren.nl/>
;bar foo"
We could also have a getElementBySelector() method, but it seems
that it would be best to let the CSSWG define that.
The specification already defined getElementsByClassName(). So, why
not getElementsBySelector() too? Or this can be better handled via
XPath expressions?
(And rightly so that it does not redefine what is allowed for
the 'class' attribute applied on elements in the XHTML 1 namespace.)
--
Anne van Kesteren
<http://annevankesteren.nl/>
e DOM interfaces
defined in DOM Level 2 HTML for it. It has nothing to do with XHTML 2.
Therefore, using "XHTML" and "5.0" should be no problem. Especially since the
HTML WG does not seem to plan to introduce any DOM interfaces for the new
elements...
--
Anne van Kesteren
<http://annevankesteren.nl/>
se of 'class' for semantic purposes.
The use of 'class' for presentation is wrong anyway (and hopefully
obsoleted in
HTML 5). And yes, although it is named incorrectly, the attribute can take
multiple, space-separated, values.
--
Anne van Kesteren
<http://annevankesteren.nl/>
Quoting Matthew Raymond <[EMAIL PROTECTED]>:
In the future, please provide the original example so that we may see
what it was before Ian agrees with you and changes it. ;)
Just read the previous draft.
--
Anne van Kesteren
<http://annevankesteren.nl/>
nowledge about every other element so
that it can correctly close all open inline elements when it sees a
tag that starts a block level element?
Mostly, yes. Most browsers have very specific behavior depending on the
element.
(Which not necessarily makes the DOM more conformant.)
Quoting David Håsäther <[EMAIL PROTECTED]>:
Basically, when the parsing section gets written, it'll be written to
match the behaviour that the most browsers do.
Why not require end-tags for all non-empty elements?
And that magically solves the parsing problem?
--
Anne van Kes
Regarding <http://whatwg.org/specs/web-forms/current-work/#the-autofocus>.
What happens when a form control is already there but its autofocus DOM
attribute is set to "true"? Same as calling the .focus() method on the form
control or same as "nothing happens"?
Ch
m that perspective
using html:menu with html:li etc. is much better I guess.
--
Anne van Kesteren
<http://annevankesteren.nl/>
f a hack. Mozilla does not represent it as a
"keygen" element
in the DOM for example, but as a select element with a _moz-type attribute set
to -mozilla-keygen. (With the attributes propagated.)
Opera does seem to have some kind of "native implementation".
* Wonders who actu
t/html" will do nothing and show
some: "this format is not supported, look for a plugin" message... I
would like
this to become a special case of as well actually. Although there is
some issue with fallback content...
--
Anne van Kesteren
<http://annevankesteren.nl/>
others also need to be updated.
--
Anne van Kesteren
<http://annevankesteren.nl/>
The description for the checkValidity() does not take into account that it can
also be called from the HTMLFormElement.
--
Anne van Kesteren
<http://annevankesteren.nl/>
ed in [HTML5].
Cheers,
Anne
--
Anne van Kesteren
<http://annevankesteren.nl/>
The specification does not really say whether it is cancelable or not
explicitly. Taking into account the text surrounding the event it is probably
not cancelable, but I guess that should be noted.
Also s/fired an/fired on/
Cheers,
Anne
--
Anne van Kesteren
<http://annevankesteren.nl/>
2.14. Extensions to the textarea element
# 'white-space' property values based on the wrap element
# for textarea elements
There is no such thing as a "wrap element".
Cheers,
Anne
--
Anne van Kesteren
<http://annevankesteren.nl/>
It only addresses form controls nested in a fieldset. However, setting optgroup
to disabled should cause descendents of that, either optgroup or option, to
become disabled as well.
--
Anne van Kesteren
<http://annevankesteren.nl/>
hat up earlier.
--
Anne van Kesteren
<http://annevankesteren.nl/>
element."
That contradicts each other, not?
--
Anne van Kesteren
<http://annevankesteren.nl/>
cription of that element (2.13) says basically the
same.
Cheers,
Anne
--
Anne van Kesteren
<http://annevankesteren.nl/>
of the object that
validity returns must return false, while the checkValidity() which is defined
in terms of validity must return true.
(There is also a markup error in 7.5. Additions specific to the
HTMLFieldsetElement interface.)
Cheers,
Anne
--
Anne van Kesteren
<http://annevankesteren.nl/>
pplications this can be
perfectly backwards compatible. Perhaps put some additional container element
around it and make optional for fallback (same as with
) and
you have some kind of solution.
Cheers,
Anne
--
Anne van Kesteren
<http://annevankesteren.nl/>
r
Since the first would only be supported by new UAs with no good
fallback, the button would be completely unnecessary.
Yeah, I meant that. And I like it now I see it :-)
--
Anne van Kesteren
<http://annevankesteren.nl/>
ou want to build real applications
on phones you need javascript. It is most likely that the Web API WG will also
investigate in this area. (Opera already does cross document messaging (from
HTML5) on some mobile phones and XMLHttpRequest etc.)
--
Anne van Kesteren
<http://annevankesteren.nl/>
n to using
then?
As noted earlier in this thread was just some random name that has to be
replaced at some point, not? Anyway, I think should be reserved for
dropdown lists, but I don't feel strongly about that.
--
Anne van Kesteren
<http://annevankesteren.nl/>
m the element and give
that element "semantic meaning". (Which is essentially what is done
today so it
is quite backwards compatible.)
--
Anne van Kesteren
<http://annevankesteren.nl/>
attribute...)
Cheers,
Anne
--
Anne van Kesteren
<http://annevankesteren.nl/>
27;DOMActivate'. (And not to the 'change' event.)
--
Anne van Kesteren
<http://annevankesteren.nl/>
?
Because per DOM3Events 'change' can not be canceled. (That is in fact
implemented.)
--
Anne van Kesteren
<http://annevankesteren.nl/>
n the html:tr element for example.
When the selector control is checked it results in the repetition
block being selected (the CSS3 ":selected" pseudo class would apply).
repeat-selection="single|multiple"
==
If you just use radio and chec
d adding an attribute to them? Maybe
that is a better solution. It would certainly degrade better than a
new input type.
Yeah, a global "label" or "for" attribute which can be applied to some
ancestor,
like html:tr. (Or only to the template (which mostly is the html:tr)
. The datalist element
and the list attribute.)
3. "The selected attribute and the form, selected,". I suggest to drop the
second "selected" or is this one of those cases were you want to be extra
explicit without it actually being necessary?
Cheers,
Anne
--
Anne van Kesteren
<http://annevankesteren.nl/>
range thing to do).
What is the reasoning? I think it is very useful that they apply to every
element, including non-XHTML elements.
--
Anne van Kesteren
<http://annevankesteren.nl/>
Quoting Ian Hickson <[EMAIL PROTECTED]>:
(Though could be replaced by
Therefore, your
statement doesn't make sense.
Or the implementation does not make sense ;-)
--
Anne van Kesteren
<http://annevankesteren.nl/>
important and when it is clear what we're supposed to do.
(Personally I can appreciate the approach Firefox took although that leaves not
much room for using them sometime in the future...)
--
Anne van Kesteren
<http://annevankesteren.nl/>
ld mean that
you are changing semantics through CSS. Something like making a link no longer
a link trhough some property.
Now there has been some need for such a language, but it is not
presentational.
It is more some semantic language to describe what kind of element it
is, which
attributes serve s
<http://whatwg.org/specs/web-apps/current-work/#the-main>
The element name should be "noframes" not "noframe".
--
Anne van Kesteren
<http://annevankesteren.nl/>
(HTMLImageElement
opr HTMLCanvasElement). I assume that in some way the resource pointed to by
HTMLImageElement.src should be used and HTMLCanvasElement.toDataURL()...
--
Anne van Kesteren
<http://annevankesteren.nl/>
the attribute does not change the state.
Testcase I used is attached. Anyone with results from other browsers?
Ian, any chance this can be incorperated in WF2 at some point so this gets
consistent? It is more or less important for dynamically testing the CSS
pseudo-classes as well as fo
Quoting Anne van Kesteren <[EMAIL PROTECTED]>:
Internet Explorer only sets defaultChecked to true when the control has a
"checked" attribute set at _parsing time_. Adding a "checked" attribute
dynamically does not change the state of defaultChecked.
It was pointed
e the image of the HTMLImageElement (or HTMLCanvasElement); that image
is unrelated to CSS. You could implement in a non-CSS UA.
Where does it say that? Could you quote that part?
--
Anne van Kesteren
<http://annevankesteren.nl/>
use for math problems, without
having to resort to MathML.
can't possibly be defined to mean two different things while staying in
the same namespace. Well, I suppose it could be based on the context it is
placed in, but I think that would get confusing. Also, there is MathML.
--
Anne van Kesteren
<http://annevankesteren.nl/>
an .
I could not find (or ) in any XHTML recommendation. I also never
encountered it anywhere as actually being used, only in some examples taken
from the XHTML 2.0 draft...
--
Anne van Kesteren
<http://annevankesteren.nl/>
r subject suggests, but it should not be
required therefore imho.
--
Anne van Kesteren
<http://annevankesteren.nl/>
y sounds suboptimal though. Especially in this situation
where you want to use an element both for mathematics and shouting...
--
Anne van Kesteren
<http://annevankesteren.nl/>
larify things?
You were talking about consistency with XHTML. Yet there has been no
recommendation or standard (whatever you prefer) that contains such an element
so the argument is bogus. on the other hand...
--
Anne van Kesteren
<http://annevankesteren.nl/>
asked you here:
<http://listserver.dreamhost.com/pipermail/whatwg-whatwg.org/>
--
Anne van Kesteren
<http://annevankesteren.nl/>
t
you want.)
--
Anne van Kesteren
<http://annevankesteren.nl/>
,
but that's not how it is. I believe UAs are free to make up alternate content
in such situations. By for example trying to get information from the file
name...
--
Anne van Kesteren
<http://annevankesteren.nl/>
invalid. I propose to allow it and have the user
agent derive some information from the image URL. This will better
reflect the real world situation: many authors actually omit alt
(which results in an invalid page) when they actually should have
written it.
HTML5 is not about making
; attribute must be ignored. Which
would imply that descendents can get focus...
--
Anne van Kesteren
<http://annevankesteren.nl/>
Quoting Matthew Raymond <[EMAIL PROTECTED]>:
Hmm... Is ever non-presentational? Radical thought: Deprecate
.
A company logo? A picture of a new product some review is about?
Depends on how
you see it I guess.
--
Anne van Kesteren
<http://annevankesteren.nl/>
Given the new parsing rules for comments (all those internal discussions...) I
was trying to write some testcases for how they are defined now.
# PASS. Well, perhaps it is, but then I'd like that to be changed. If we take
the problematic snippet:
# PASSFAIL" for:
#
Quoting Anne van Kesteren <[EMAIL PROTECTED]>:
However, from the specification it is not entirely clear what should
happen with
s. is just
easy to author, widely implemented and well supported and therefore it is in
the draft if I recall correctly. If backwards compatibility wasn't a concern I
would not see so many reasons to keep it either...
--
Anne van Kesteren
<http://annevankesteren.nl/>
In <http://whatwg.org/specs/web-forms/current-work/#relation> I think the text
on :required and :optional should be clarified so that it is clear that these
pseudo-classes only apply to elements to which the "required" attribute
applies.
--
Anne van Kesteren
<http://annevankesteren.nl/>
Currently the Web Forms 2 draft has both a valueMissing flag and a missingValue
flag. They are supposedly identical. Opera has currently support for
valueMissing (that's also what the (not yet public) test suite is testing), but
both are easy to "fix".
--
Anne van
Quoting Anne van Kesteren <[EMAIL PROTECTED]>:
In <http://whatwg.org/specs/web-forms/current-work/#relation> I think
the text
on :required and :optional should be clarified so that it is clear that these
pseudo-classes only apply to elements to which the "required" attr
CRASHED!
Opera 9/Mac: CRASHED!
Interesting. Note that these are not final versions. (Newer internal versions
don't have this crash and do the same as Opera 8.5. As in, not exposing it in
the DOM.
--
Anne van Kesteren
<http://annevankesteren.nl/>
t node nor of the document the node is in).
However, I'm still not sure what problem is being solved here.
--
Anne van Kesteren
<http://annevankesteren.nl/>
d of section 2.3? Or
does that not apply to this attribute value?
--
Anne van Kesteren
<http://annevankesteren.nl/>
want the parser to do? And
also there is talk about whitespace between -- and > but currently all
kinds of
chracters are allowed there (including - for instance).
--
Anne van Kesteren
<http://annevankesteren.nl/>
iews-AbstractView-document
--
Anne van Kesteren
<http://annevankesteren.nl/>
e
elements are missing and some controls need to be covered as well.
Feedback, new tests and other things are appreciated.
--
Anne van Kesteren
<http://annevankesteren.nl/>
ite a few tests.
Otherwise good work, I'm glad to finally see the beginnings of a test suite.
Thanks.
--
Anne van Kesteren
<http://annevankesteren.nl/>
al" comment handling for the
moment. So you could use Opera 8.5 if you do not want SGML comment handling.
--
Anne van Kesteren
<http://annevankesteren.nl/>
ext: Y
And this likely breaks existing content. Perhaps not for EM, but certainly for
other inline elements, like .
--
Anne van Kesteren
<http://annevankesteren.nl/>
s so parsers did funny things on error
recovery.
--
Anne van Kesteren
<http://annevankesteren.nl/>
in the document. (Multiple IDs for the same element
is less of a problem imho.)
--
Anne van Kesteren
<http://annevankesteren.nl/>
would have to be reparsed when the user disables scripting or
frames.
--
Anne van Kesteren
<http://annevankesteren.nl/>
e if it is implemented in the first place.
element
This element is closed by , , and . Using or
also closes the parent element of .
element
This element is closed by , , , , and Same as
with .
element
element
Both are unsupported and treated as unrecognized elements.
--
Anne van Kesteren
<http://annevankesteren.nl/>
tation feedback
(This is not specific to this feature.)
--
Anne van Kesteren
<http://annevankesteren.nl/>
ng the
specification to be compatible with Opera 9 and Safari given that what they do
is sensible.
--
Anne van Kesteren
<http://annevankesteren.nl/>
Quoting Jim Ley <[EMAIL PROTECTED]>:
I simply don't see the value in standardising the error behaviour here.
Just setting it to 1, which is an appropriate value, does not give
interoperable
behavior either. (The selected option is not the same.)
--
Anne van Kes
Quoting Jim Ley <[EMAIL PROTECTED]>:
On 2/11/06, Anne van Kesteren <[EMAIL PROTECTED]> wrote:
Quoting Jim Ley <[EMAIL PROTECTED]>:
I simply don't see the value in standardising the error behaviour here.
Just setting it to 1, which is an appropriate value, does not give
Quoting Ian Hickson <[EMAIL PROTECTED]>:
The first draft of the HTML5 Parsing spec is ready.
Great!
It's not 100% complete. Some of the things that need work are:
Interaction with document.open/write/close is undefined
How to determine the character encoding
Integration with quirks mo
d have this implemented correctly...
--
Anne van Kesteren
<http://annevankesteren.nl/>
February
as opposed to the one from 22 February 2006...
Best thing would be if there was some list to which CVS diff-logs would be
e-mailed or so. Would make it a lot easier to track changes.
--
Anne van Kesteren
<http://annevankesteren.nl/>
Quoting ROBO Design <[EMAIL PROTECTED]>:
<...>
What's wrong with using the "form" attribute to point to multiple forms? One
submits to one place, the other submits to another place.
--
Anne van Kesteren
<http://annevankesteren.nl/>
d put in a local version to assist
with making test-cases of the spec.
Feel free to download a weekly build of Opera 9.0:
http://my.opera.com/desktopteam/
... and test how it works.
--
Anne van Kesteren
<http://annevankesteren.nl/>
van Kesteren
<http://annevankesteren.nl/>
strings instead.
Can this be clarified?
--
Anne van Kesteren
<http://annevankesteren.nl/>
Quoting Henri Sivonen <[EMAIL PROTECTED]>:
Shouldn't lang take precedence in HTML?
I'd be opposed to that. At least two UAs have implemented the opposite.
("xml:lang" taking precedence over "lang".)
--
Anne van Kesteren
<http://annevankesteren.nl/>
list since
neither nor can't contain ... Can this be helped
somehow?
That could be solved using an attribute I guess, similar to "edit" in
some XHTML
2.0 proposal. Inserting and removing table cells on the other hand...
--
Anne van Kesteren
<http://annevankesteren.nl/>
1 - 100 of 1841 matches
Mail list logo
