Quoting Anne van Kesteren <[EMAIL PROTECTED]>:
Quoting Hallvord R M Steen <[EMAIL PROTECTED]>:
This doesn't describe UA behaviour according to my test cases. What
current UAs do is to ignore nested *start* tags. They do not
close the outer form before the start tag of the inn
inner form.
I think you are confusing HTML with XHTML here. At least, I hope you do.
Cheers,
Anne
--
Anne van Kesteren
<http://annevankesteren.nl/>
fox lowercases all unknown and known attributes. It seems that
Opera and Internet Explorer lowercase all known attributes unless they are
created using createAttribute. Opera and Internet Explorer do not touch unknown
attributes.
--
Anne van Kesteren
<http://annevankesteren.nl/>
Henri Sivonen wrote:
I added bgsound to the elements that do not close head.
I think you leave out presentational elements. I am pretty sure HTML 5
will not introduce html:bgsound.
--
Anne van Kesteren
<http://annevankesteren.nl/>
. Neither the option element or optgroup element is mentioned.
[1]<http://whatwg.org/specs/web-forms/current-work/#disabled>
[2]<http://whatwg.org/specs/web-forms/current-work/#relation>
--
Anne van Kesteren
<http://annevankesteren.nl/>
s contact information.
Of the particular section. I suppose you could nest ADDRESS inside BLOCKQUOTE
and have the effect. Anyway, did you miss my point about the
information should
be visible?
--
Anne van Kesteren
<http://annevankesteren.nl/>
lready possible using BLOCKQUOTE, CITE and perhaps ADDRESS.
It is also unclear to me how this is related to Web Forms 3 in any way.
Kind regards,
Anne
--
Anne van Kesteren
<http://annevankesteren.nl/>
works. "foo bar" means the element has two
classes bound to it, "foo" and "bar". With your syntax,
getElementsByClassName("bar foo") would also need to match an element
with "foo
bar" as value for the CLASS attribute.
Kind regards,
Anne
--
Anne van Kesteren
<http://annevankesteren.nl/>
- HEAD
- - TITLE
- BODY
- - SECTION
... imho.
Kind regards,
Anne
--
Anne van Kesteren
<http://annevankesteren.nl/>
nces. Or perhaps just require them for some elements,
like the P element.
Should (in memory of HTML 4.01 Transitional) character data imply the
start of body?
It should be non conforming, but it should be parsed that way. (Both
are should
for readability.)
Kind regards,
Anne
--
Anne va
o a relative
one later on.
I think the current definition is better and more correct.
--
Anne van Kesteren
<http://annevankesteren.nl/>
new things,
'contentEditable' and 'execCommand' have been here for years.
Desktop browsers are not likely to implement all kinds of fancy new
stuff. They rather support things when it increases support for
applications/sites out there.
Kind regards,
Anne
--
Anne
ves to REC, which is not very likely I suppose.)
Kind regards,
Anne
--
Anne van Kesteren
<http://annevankesteren.nl/>
cripting for editing anyway I drop my proposal.
(You probably want to store the DOM of the entire page anyway.)
Kind regards,
Anne
--
Anne van Kesteren
<http://annevankesteren.nl/>
; attribute are not equivalent.
Internet Explorer does have a global 'disabled' attribute by the way, I
have not tested 'readonly' yet. Also, editable areas do not have to act
the same as form controls, they are different things. Editing a web page
(document) is different from
contentEditable is much better than a textarea hack.
Submission could be handled using the 'form' attribute as suggested
earlier in this thread by Hallvord Reiar Michaelsen Steen. (Perhaps
allowing the 'name' attribute as well to make it even better.)
Kind regards,
Dimitri Glazkov wrote:
I was thinking more along of the lines of this:
...
Perhaps we should allow the 'form' attribute from Web Forms 2 on all
elements that have the 'contenteditable' attribute set.
That would neatly solve the problem.
Kind regards,
Anne
-
the 'input' event defined here:
<http://whatwg.org/specs/web-forms/current-work/#the-change>.
Kind regards,
Anne
--
Anne van Kesteren
<http://annevankesteren.nl/>
I propose to rename the "currentFocus" attribute to "activeElement" for
historical reasons.[1] (Both Internet Explorer and Opera implement it in
that way.)
Kind regards,
Anne
[1]<http://msdn.microsoft.com/workshop/author/dhtml/reference/properties/activeelement.asp&g
Neither is particularly extensive and only covers some of the basics.
Eventually tests will be collected and made available through
whatwg.org as far
as I understand it.
Kind regards,
Anne
--
Anne van Kesteren
<http://annevankesteren.nl/>
accept type of text/html, which would allow a UA to load
any external editor (eg. XStandard) or degrade to a regular text area?
You can not restrict certain elements from being edited?
Kind regards,
Anne
--
Anne van Kesteren
<http://annevankesteren.nl/>
Why does Web Forms 2 not deal with the textInput event from DOM Level 3 Events?
<http://www.w3.org/TR/DOM-Level-3-Events/events.html#event-textInput>
Kind regards,
Anne
--
Anne van Kesteren
<http://annevankesteren.nl/>
non-namespaces attributes specified by the way? That
seems to be undefined. (I admit that I have not read it carefully.)
Kind regards,
Anne
--
Anne van Kesteren
<http://annevankesteren.nl/>
x27;s it good for?
Could you be more specific? It basically enables WYSIWYG editing for
web pages.
(With the freedom that you can restrict certain elements from being edited, et
cetera.)
Kind regards,
Anne
--
Anne van Kesteren
<http://annevankesteren.nl/>
Quoting Anne van Kesteren <[EMAIL PROTECTED]>:
Should it fall back to its initial value which is defined
to be equivalent to the value of the MIN attribute or should something else
happen?
Found this:
# For value attributes that are invalid according to the min, max, step,
# maxlengt
e, but the control is left with no
# value selected.
If type=range is also excluded from the second sentence, which is the part that
is unclear to me, the user interface should probably show the specified value
as well although it is out of range and make it clear that it is not
submitable?
--
An
e. In
an editor you want to edit what you see and what will be the end result, if you
add :read-write you are thinking about the end result, not editing environment.
See also: <https://bugzilla.mozilla.org/show_bug.cgi?id=302188#c17>
Kind regards,
Anne
--
Anne van Kes
Quoting Kornel Lesinski <[EMAIL PROTECTED]>:
This makes a lot of sense on forms like:
This represents essentially two forms. It does not make sense it all if a
developer writes such forms.
--
Anne van Kesteren
<http://annevankesteren.nl/>
ail' or 'test'.
Firefox and IE act identically.
So the definition of the disabled content attribute should be changed and
perhaps some other things should be clarified as well. This was merely a
survey.
--
Anne van Kesteren
<http://annevankesteren.nl/>
Quoting Anne van Kesteren <[EMAIL PROTECTED]>:
Example document:
#
#
#
#
#
#
#
(1) When t1 is focused the default submit button in IE is s2 and in Opera and
Firefox it is s1 but disabled so it does not work.
(2) When t2 is focused the default submit button in IE, Opera and
F
read-only. So
anything that matches :disabled will match :disabled:read-only but not the
other way around.
However, taking <https://bugzilla.mozilla.org/show_bug.cgi?id=271720#c33> into
account it might be that more pseudo-classes will eventually come up.
All these
things should be clar
,
Anne
--
Anne van Kesteren
<http://annevankesteren.nl/>
.com/pipermail/whatwg-whatwg.org/2005-January/002993.html>
--
Anne van Kesteren
<http://annevankesteren.nl/>
Quoting Christoph Päper <[EMAIL PROTECTED]>:
Anne van Kesteren:
It appears that no browser has implemented the 'may' from HTML4
Confusingly (at least) Firefox 1.04 does trim tabulators and
newlines, but not spaces, and only in HTML mode, not in XML mode.
<http://webdes
error/002.html>
For XHTML, however, UAs do different things:
<http://annevankesteren.nl/test/html/wf2/error/002.xht>
Opera does not render OPTGROUP elements and Firefox has some default styling.
Selection seems also to be different. Are these to be considered bugs?
--
Anne
* More SGML comments with thoughts.
* More nodes.
--
Anne van Kesteren
<http://annevankesteren.nl/>
ute type _is_ CDATA and (2)
this is not about XML. (At least, not yet.)
--
Anne van Kesteren
<http://annevankesteren.nl/>
erfectly maps to expected behavior and implemented behavior.
I see no
reason not to make this as strict and simple as possible.
--
Anne van Kesteren
<http://annevankesteren.nl/>
From:
<http://whatwg.org/specs/web-forms/current-work/#methodAndEnctypes>
# The value of the enctype attribute must be dispatched using a
# case-insensitive literal comparison.
What exactly does this mean, in terms of Unicode?
Kind regards,
Anne
--
Anne van Kesteren
It should basically not happen at all. It appears that no browser has
implemented the 'may' from HTML4 and therefore we can now say browsers must not
trim.
Examples:
checkbox:
...
no checkbox:
...
Kind regards,
Anne
--
Anne van Kest
What exactly should happen here:
<http://annevankesteren.nl/test/html/wf2/select/007>
Kind regards,
Anne
--
Anne van Kesteren
<http://annevankesteren.nl/>
Say I load this file through a DATA attribute of a SELECT element:
http://www.w3.org/1999/xhtml";>
FAIL
PASS
Should it say PASS? Is it undefined? Is there a specification which defines
this?
Kind regards,
Anne
--
Anne van Kesteren
<http://annevankesteren.nl/>
Quoting Anne van Kesteren <[EMAIL PROTECTED]>:
Would it be possible to add a print stylesheet to the specifications?
Or perhaps
a global one although that is not stricly necessary. (PDF would be
even cooler,
but I'm not sure if there are any good scripts for that you could
Any chance Web Forms 2 is going to say something about:
Default value for size DOM attribute from the SELECT element
Test
alert(document.getElementsByTagName('select')[0].size);
Firefox 1.8b3: -1.
Opera 8 and IE 6: 0.
Haven't been able to test other browsers.
--
Anne van
bably won't work in existing browers...)
--
Anne van Kesteren
<http://annevankesteren.nl/>
Would it be possible to add a print stylesheet to the specifications? Or perhaps
a global one although that is not stricly necessary. (PDF would be even cooler,
but I'm not sure if there are any good scripts for that you could add to the
publishing mechanism.)
--
Anne van Kesteren
everal seconds) gives a total of
218 pages. Like the W3C specs, it would be so much better if each
section were split into separate pages.
I'm opposed to that. Separate sections in separate documents make reading the
draft a pain. (I have argued otherwise in the past...)
--
Anne van Kes
foobar
Same thing happens I guess when you have additional rows with repeat="{integer}"
set I guess.
(It might also be that I got lost somewhere in the specification. As it is quite
difficult to follow with 18 different steps. (Based on the source version.))
--
Anne van Kest
Quoting Matthew Raymond <[EMAIL PROTECTED]>:
You can do that with css anyway, what is your point?
That CSS can be overridden by the user stylesheet?
Userbase: 2. (Both are geek.)
--
Anne van Kesteren
<http://annevankesteren.nl/>
ptional feature.
--
Anne van Kesteren
<http://annevankesteren.nl/>
rounds
are used for IEs implementation, what those workarounds are, etc. That way we
can define a better behavior for browsers implementing the specification.
--
Anne van Kesteren
<http://annevankesteren.nl/>
moment this is not particularly clear
and it would be nice to know.
--
Anne van Kesteren
<http://annevankesteren.nl/>
Quoting Christian Biesinger <[EMAIL PROTECTED]>:
Anne van Kesteren wrote:
Certain DOM attributes such as the href DOM attribute[1] are implemented
differently than specified. The attribute is implemented as to return a
resolved link, not as equivalent to the href HTML attribute.
The &q
Shouldn't the print method on the window DOM interface be defined as well?
Example: print
--
Anne van Kesteren
<http://annevankesteren.nl/>
//www.w3.org/TR/DOM-Level-2-HTML/>
--
Anne van Kesteren
<http://annevankesteren.nl/>
d and I'm not sure
if it also works with Flash, but I guess it does.)
--
Anne van Kesteren
<http://annevankesteren.nl/>
Matthew Raymond wrote:
Let's look at these pseudoclasses one at a time...
If you are to propose CSS I suggest you mail [EMAIL PROTECTED] instead.
--
Anne van Kesteren
<http://annevankesteren.nl/>
).
He's correct for a bit though. If you have the following element:
Foo bar, etc.
You could easily remove that DIV from the flow using javascript. And
when javascript is disabled it would show up. Of course, compared to
NOSCRIPT this is suboptimal at best.
--
Anne van Kesteren
r in these slides:
http://www.w3.org/2005/Talks/04-19-steven-XHTML2-XForms/
I don't really see what else to use for those.
Why doens't SECTION suffice? They are sections separated by decoration.
At least, that is how it appeals to me.
--
Anne van Kesteren
<http://annevankesteren.nl/>
Mikko Rantalainen wrote:
You cannot put a random string between and tags
either and expect to get a valid XML fragment as a result.
True, that's why htmlspecialchars was created (in PHP). (Note that there
are five predefined entities in XML of which " is one.)
--
Anne van Keste
ent doesn't seem like a good thing.
(I'm aware of possible solutions. It's just that you don't normally
think of this. Even Tim Bray - editor of the XML specification - called
it "broken as designed".)
--
Anne van Kesteren
<http://annevankesteren.nl/>
update to the specification to have a
hidden TEXTAREA. (Such a TEXTAREA can be implemented now using:
foo.)
There was a similar problem with the XHTML admin of Movable Type as
described here:
<http://golem.ph.utexas.edu/~distler/blog/archives/000564.html>
--
Anne van Kes
n what it means when one element has
'1' and another has '4'. I might have missed it but I don't see which is
supposed to be more important.
I was also wondering about inheritance.
--
Anne van Kesteren
<http://annevankesteren.nl/>
-
colspan attributes with values that don't convert to numeric 1?
This would mean checking the first child of the TBODY element for the
amount of TD children it has. Not?
--
Anne van Kesteren
<http://annevankesteren.nl/>
he BOM of UTF-8 instead of this I guess.
--
Anne van Kesteren
<http://annevankesteren.nl/>
algorithm.
Datagrids in common GUIs aren't capable of complex column captions
like the above. How would you change the spec to work with the above?
Don't check THEAD for such data.
And also, perhaps it would be useful to check COLGROUP and COL elements
first...
--
Anne
2.2>
[2]<http://www.letselplein.nl/~exemplarisch/sort-table/sort-table-rows.html>
--
Anne van Kesteren
<http://annevankesteren.nl/>
ibute
and explicit support for xml:base?
<http://whatwg.org/specs/web-apps/current-work/#the-base>
States that for XML documents you must use xml:base and must not use
xhtml:base.
--
Anne van Kesteren
<http://annevankesteren.nl/>
Ian Hickson wrote:
5. Treat as
The only exception, I believe, would be for , which would
instead be treated as .
But as the BORDER attribute is not part of HTML5 that is for someone
else to specify. Not?
--
Anne van Kesteren
<http://annevankesteren.nl/>
fantasai wrote:
*Why?* Why of all things would you choose to interpret it like /that/?
It's neither reporting a useful error, nor handling it per SGML rules.
Because that is expected.
--
Anne van Kesteren
<http://annevankesteren.nl/>
|checkbox="checkbox"| is not a valid
attribute and not a valid attribute value of the invalid attribute as
far as I know.
Or did you mean something else by 4? (It might be that we just agree...)
--
Anne van Kesteren
<http://annevankesteren.nl/>
ng to represent. I'm not
sure if I understand this correctly.
--
Anne van Kesteren
<http://annevankesteren.nl/>
editable) but it creates another problem
namely that people can insert new definitions.
Again, a DI element would solve the issue.
--
Anne van Kesteren
<http://annevankesteren.nl/>
alking
about conformance checkers and not about parsers.
--
Anne van Kesteren
<http://annevankesteren.nl/>
f this
somehow gets through then please choose the OBJECT element instead.
--
Anne van Kesteren
<http://annevankesteren.nl/>
transformed into an
image gallery.
Such things are already possible using CSS and XBL. This would be abuse
of the CANVAS element as noted in the beginning of the section.
--
Anne van Kesteren
<http://annevankesteren.nl/>
e("SomeOldClass")
* someElement.className.hasClass("someClass")
This would be useful.
* The lack of min-width and max-width in IE's CSS makes things difficult.
There are hacks for this.
--
Anne van Kesteren
<http://annevankesteren.nl/>
x27;t really given the syntax a thought as
James Graham points out. Excluding some elements may be nice, but you
probably want to restrict attributes or even element/attribute values as
well.
--
Anne van Kesteren
<http://annevankesteren.nl/>
rnate renderings (such as voice).
The content from the CANVAS element is the fallback content.
... alternate content ...
--
Anne van Kesteren
<http://annevankesteren.nl/>
this content model.
For example, you could allow any element that is allowed as a child of
the particular element that has contentEditable set, but there should be
a way to exclude certain elements (and perhaps attributes) if you don't
want those.
--
Anne van Kesteren
Ian Hickson wrote:
On Mon, 18 Apr 2005, Anne van Kesteren wrote:
Now I know backwards compatibility is important[1], but DEL and INS
are insanely complex to use and do not cover all "edit" use cases.
Can you give some examples they don't cover?
Well, cases were you just want to note
Is HTML5 going to deal with the quote problem? Or will the CSS WG
introduce ::first-character and ::last-character to deal with that?
(I did check the source for XXX comments regarding quotes, but I
couldn't find any.)
--
Anne van Kesteren
<http://annevankesteren.nl/>
ly present that information to the user using CSS or some
other mechanism. INS and DEL are IMHO not really appropriate for those
kind of edits.
[1]<http://ln.hixie.ch/?start=1113762425&count=1>
--
Anne van Kesteren
<http://annevankesteren.nl/>
ml:lang is for X(HT)ML only.
Done.
I think the heading for the attribute defintion should be updated
to include xml:lang as well.
Done.
I assume we are going to do something similar for 'xml:id' when that
becomes REC? Or do the issues with regard to type ID need to be sorted
out
particular example from the spec.
I think it should be kept. But that there should be a similar note like
the one about DFN.
--
Anne van Kesteren
<http://annevankesteren.nl/>
markup design in humble opinion. (Although it also has some
advantages.)
--
Anne van Kesteren
<http://annevankesteren.nl/>
in all other languages. I think this is exactly what the
# i tag was invented for.
<http://annevankesteren.nl/archives/2003/09/b-svg-and-accessibility#comment-206>
--
Anne van Kesteren
<http://annevankesteren.nl/>
attribute.
You could also say something like: "A visual UA might display || as: [example rendering]" where
[example rendering] is an image of a link with a PDF icon after it.
--
Anne van Kesteren
<http://annevankesteren.nl/>
'. What would be the combined semantics of
|rel="index prev"| or |rel="prev index"|...
--
Anne van Kesteren
<http://annevankesteren.nl/>
ntion with another link type, an
alternate version of the resource type indicated.
(that definition is not perfect, but I think you'll understand what its
supposed to mean anyway)
I do, but I'm not sure if it would be correct.
--
Anne van Kesteren
<http://annevankesteren.nl/>
details right now...
... but this looks like a very ugly markup construct...
however, he was of course wrong, as this kind of nesting is actually
kind a cool, not?
..? It looks terrible imho. Not something you put inline or so.
--
Anne van Kesteren
<http://annevankesteren.nl/>
ix that (and others, if they exist) ambiguity first.
Also note that we probably don't need |rel="permalink"| as the link
inside an ARTICLE element with a value of "bookmark" probably does that
already.
--
Anne van Kesteren
<http://annevankesteren.nl/>
bute links to the CITE element...
* 2.6.16. The cite element
Could this element get a note saying that it should not be used for
quotations. Perhaps an invalid example would help as well.
--
Anne van Kesteren
<http://annevankesteren.nl/>
The links to the diff files:
<http://whatwg.org/specs/web-forms/current-work/>
... are both broken.
--
Anne van Kesteren
<http://annevankesteren.nl/>
at I
just wrote it might be wort to make it more explicit.
--
Anne van Kesteren
<http://annevankesteren.nl/>
at does an element with no href="" represent?
Nothing? Or I guess we could make the href="" attribute required.
With nothing it represents a semantically meaningless element, like
SPAN. Making the HREF attribute required seems like a good thing to do.
--
Anne van Kesteren
<http://annevankesteren.nl/>
eally used.)
--
Anne van Kesteren
<http://annevankesteren.nl/>
r hand, if it couldn't be produced that way, it probably
wouldn't be that sucessful.
--
Anne van Kesteren
<http://annevankesteren.nl/>
their comments
public?
Also it seems the W3C has a lot of demands that could slow down the
process. Will the call for implementations draft be even more postponed
or is it still underway?
Overall it seems like a good thing though.
--
Anne van Kesteren
<http://annevankesteren.nl/>
to the elements that are allowed in that section. Not just some
examples, but making a list of them.
--
Anne van Kesteren
<http://annevankesteren.nl/>
1 - 100 of 154 matches
Mail list logo
