On Mon, 30 Jan 2006, Simon Pieters wrote:
What should happen with comments that contain -- when you serialize
the DOM into HTML? When serializing into XML it should result in a fatal
error according to DOM3Core[1], but I guess that is not really desired
for HTML. Should the comment be
On Jun 5, 2007, at 09:38, Ian Hickson wrote:
On Sat, 23 Apr 2005, Henri Sivonen wrote:
On Mar 31, 2005, at 12:32, fantasai wrote:
So, for example, I could use attribute minimalization to shorten the
'type=checkbox' part like so:
input checkbox checked
What should text/html flavor HTML5
On Jun 1, 2007, at 09:34, Ian Hickson wrote:
I don't know which section this is talking about.
It was about datagrid.
Is it better now?
I think the non-normative intro section still doesn't sufficiently
cover
the relationship to the DOM and the CSS frame tree.
The relationship to CSS
Hello,
I have a request and a question about Web Form attributes:
--- minlength ---
I'd like to see a minlength attribute that can be used on the same
elements as the maxlength attribute. The default value can be 0 unless
the required atribute is set (in that case it should be 1). The value
I can give you my opinions. Not sure if they match up with Ian's or
not. :)
On Jun 6, 2007, at 2:41 AM, Henri Sivonen wrote:
* When the data source was initialized from the DOM, will changes
to the datagrid be reflected back to the DOM?
I would expect a DOM data source to be updated.
On Wed, 06 Jun 2007 12:56:23 +0200, Sander [EMAIL PROTECTED] wrote:
--- minlength ---
I'd like to see a minlength attribute that can be used on the same
elements as the maxlength attribute. The default value can be 0 unless
the required atribute is set (in that case it should be 1). The value
of
Hello,
I have a question about the change event.
The specs say that for select ...the change event shall be fired when
the selection is completed Does this mean that, when using a
keyboard for navigation, the change event is fired when the user hits
'enter' or when she navigates from one
Anne van Kesteren schreef:
On Wed, 06 Jun 2007 12:56:23 +0200, Sander [EMAIL PROTECTED] wrote:
--- minlength ---
I'd like to see a minlength attribute that can be used on the same
elements as the maxlength attribute. ...
Why can't you use pattern= for this?
Maybe I could use that, but as a
On Wed, 06 Jun 2007 14:15:02 +0200, Sander [EMAIL PROTECTED] wrote:
Why can't you use pattern= for this?
Maybe I could use that, but as a front-end developer I'm not aware of
all the possibilities and grammar of regular expressions (as goes for a
lot of front-end developers I guess, even
Anne van Kesteren schreef:
Why can't you use pattern= for this?
Maybe I could use that, but as a front-end developer I'm not aware of
all the possibilities and grammar of regular expressions (as goes for
a lot of front-end developers I guess, even proffessionals).
I guess pattern can be
2007/6/6, Sander:
Anne van Kesteren schreef:
Why can't you use pattern= for this?
Maybe I could use that, but as a front-end developer I'm not aware of
all the possibilities and grammar of regular expressions (as goes for
a lot of front-end developers I guess, even proffessionals).
I
Thomas Broyer schreef:
2007/6/6, Sander:
But if you can use pattern to define a minimal length, than I'm sure you
can define a minimal length bigger than 0, which makes it required.
No, because Controls with no value selected do not need to match
their pattern. (Although if they are required
2007/6/6, Sander:
Thomas Broyer schreef:
Yes, minlength could be handy, but pattern=.{3,} is not that
difficult (equivalent to minlength=3 here).
I see it's not really difficult, that's true (as I said before, I don't
know much about regular expressions). But as I more than once heard the
On Wed, 06 Jun 2007 08:11:05 +0200, Ian Hickson [EMAIL PROTECTED] wrote:
The spec says:
# If the element's contents are not conformant, it is possible that
# the roundtripping through innerHTML will not work. For instance, if
# the element is a textarea element to which a Comment node has been
On Fri, 10 Mar 2006, Alexey Feldgendler wrote:
Does the current version of the spec define what happens to elements
with duplicate ID values?
No. It's something we should consider for fixes to DOM3 Core, though.
The problem of duplicate ID isn't just another issue where it's nice to
have
On Thu, 07 Jun 2007 00:20:18 +0200, Ian Hickson [EMAIL PROTECTED] wrote:
Preventing such attacks by a HTML cleaner would require either making a
full list of all forbidden IDs, class names etc, or imposing Draconian
rules upon user-supplied content, completely disallowing such useful
attributes
On Sun, 12 Mar 2006, Lachlan Hunt wrote:
[The spec] does not cover [entities for] the characters in the range
from #x80 to #x9F, which have historically been treated as code points
from the Windows-1252 repertoire, rather than the control characters
from Unicode. AFAIK, this is already
On Wed, 6 Jun 2007, Henri Sivonen wrote:
Requiring lower case for the boolean attribute's canonical name (as
value) certainly makes things friendly for clean and portable RELAX NG
schemata and, thus, easier for me. It also makes things politically
correct as far as XHTML5 goes. I can
On Thu, 7 Jun 2007, Alexey Feldgendler wrote:
On Thu, 07 Jun 2007 00:20:18 +0200, Ian Hickson [EMAIL PROTECTED] wrote:
Preventing such attacks by a HTML cleaner would require either
making a full list of all forbidden IDs, class names etc, or
imposing Draconian rules upon
On Thu, 16 Mar 2006, Henri Sivonen wrote:
From the spec:
The term validation specifically refers to a subset of conformance
checking that only verifies that a document complies with the requirements
given by an SGML or XML DTD. Conformance checkers that only perform
validation are
On Thu, 16 Mar 2006, Henri Sivonen wrote:
At the end of section 1.8 it says:
These XML documents may contain a DOCTYPE if desired, but this is not
required to conform to this specification.
I'd like to see a note here. Something like this: Note: According to
[XML], XML processors are not
On Sun, 19 Mar 2006, Henri Sivonen wrote:
Since U+ has no legitimate reason to be there just to get dropped,
is any encounter of U+ a parse error?
Yes. Fixed.
The way the spec is written, U+000D does not occur in the character
stream immediately before tokenization, but (as in
On Mon, 20 Mar 2006, Lachlan Hunt wrote:
I'm just wondering how you're intending to deal with basefont? AFAIK,
the only browser that supports it these days is IE, but it does so by
breaking the DOM (I could be mistaken, but I think NN4 supported it
too).
Considering that no other modern
Ian Hickson wrote:
On Sun, 12 Mar 2006, Lachlan Hunt wrote:
Characters in the range from #x01 to #x19 (except for whitespace
characters) are not treated interoperably across platforms...
The use of characters in either of these ranges should be an easy parse
error.
I've made the first set
Thomas Broyer schreef:
... Even though there
are only 5 characters... if it has no meaning to someone they can easily
make mistakes: {3,}. or ,{3.}. Easy as it is, this stuff is
abrcadabra to a lot of authors.
Given that:
If the pattern given by the attribute specifies a pattern that is
Le 2007-06-06 à 6:56, Sander a écrit :
I'd like to see a minlength attribute that can be used on the same
elements as the maxlength attribute.
I'm not sure a minlength attribute like this can be consistent with
maxlength.
The maxlength attribute prevents users from entering more
26 matches
Mail list logo
