On Sat, 4 Feb 2006, Bjoern Hoehrmann wrote:
>>
>> It's mathematically impossible to verify that all script on the page is
>> always going to generate conformant DOMs, but indeed, a validator that
>> attempts it should be given high marks.
>
> Well, if you approach the problem by asking whether i
* Ian Hickson wrote:
>On Fri, 3 Feb 2006, Blanchard, Todd wrote:
>> You are assuming that validators run javascript - they generally don't.
>> I'm hoping to add it to Scrutinizer
>> (http://www.blackbagops.net/seaside/html) but that would make it unique
>> in the world of validators.
>
>It's mat
On Fri, 3 Feb 2006, Blanchard, Todd wrote:
>
> You are assuming that validators run javascript - they generally don't.
> I'm hoping to add it to Scrutinizer
> (http://www.blackbagops.net/seaside/html) but that would make it unique
> in the world of validators.
It's mathematically impossible to
On Fri, 3 Feb 2006, Gervase Markham wrote:
>
> Simon Pieters wrote:
> > Browsers could mark all errors as red in view source. In Firefox you can
> > select a piece of text and view selection source, which will bring up
> > the serialized DOM.
>
> They could (at least, as far as I understand the i
On Thu, 2 Feb 2006, Blanchard, Todd wrote:
>
> OK, I have to disagree with this - the id's MUST NOT be duplicated as
> the end result is simply converting one kind of error to a different
> kind of error.
I don't understand why this is bad. The document isn't even well-formed in
these cases, if
On Thu, 2 Feb 2006, David Hyatt wrote:
>
> BTW, we tried to add as an inline that should be reopened (like
> and etc.) and it broke some of our layout tests (snippets of
> real-world Web sites). clearly does not always reopen in WinIE
> and Firefox, so for now we are having to leave it out.
On Thu, 2 Feb 2006, Blanchard, Todd wrote:
>
> What I want to know is: if the "cloned" node has an id attribute, and
> id is meant to be unique, then how do we resolve this conflict?
We don't. For compatibility with existing implementations we are forced to
require that the ID be duplicated too
Lachlan Hunt wrote:
For example, using this CSS-like syntax (but it's not CSS).
selector {
event-name: function();
}
I just remembered BECSS, which is pretty much that exact thing. Strange
how didn't occur to me at all, though it must have been buried in my
subconscious somewhere :-).
h
On Feb 3, 2006, at 9:30 AM, Jim Ley wrote:
On 2/3/06, Gervase Markham <[EMAIL PROTECTED]> wrote:
Jim Ley wrote:
the document of course shows no use cases at all.
Is there some doubt that the ability to tag an arbitrary set of
elements
and later easily get an array of those elements is a u
Jim Ley wrote:
On 2/3/06, Michel Fortin <[EMAIL PROTECTED]> wrote:
Le 2006-02-03 à 09:30, Jim Ley a écrit :
So to generalize the use case, when I want to attach an event to a
child element or an element linked by any other mean to the element
having that class, I can't use addEventListenerToClas
On 1/30/06, Ric Hardacre <[EMAIL PROTECTED]> wrote:
> hello, i'm an asp developer in the uk and have a couple of
> suggestions... no doubt selfishly to make my life easier one day :-)
> these could probably do with their own threads if they're deemed worthy
> of discussion but let's just throw them
On 2/3/06, Jim Ley <[EMAIL PROTECTED]> wrote:
> On 2/3/06, Gervase Markham <[EMAIL PROTECTED]> wrote:
> > Jim Ley wrote:
> > > Yes, but they're all using it to attach events to every one of the
> > > class, which is why you have to look at use cases, the reason they're
> > > doing it is not because
Gervase Markham wrote:
Brad Fults wrote:
I see this is still an open issue[1]. Is this now implemented as #1
(space-delimited class names to match)?
I suggest either going with the space-delimited approach (as it's
language-agnostic and well-defined at least) or with Aankhen's
suggestion of a
hello, i'm an asp developer in the uk and have a couple of
suggestions... no doubt selfishly to make my life easier one day :-)
these could probably do with their own threads if they're deemed worthy
of discussion but let's just throw them out there:
1. form tag:
send="all" , (default, send
Hi,
From: Michel Fortin <[EMAIL PROTECTED]>
I have a some markup like this:
Tab 1
Tab 2
...
...
With the help of a style sheet, the script transforms this into some sort
of tab view. It search for each div of class "pane". It lo
Le 2006-02-03 à 11:37, Jim Ley a écrit :
On 2/3/06, Michel Fortin <[EMAIL PROTECTED]> wrote:
Le 2006-02-03 à 09:30, Jim Ley a écrit :
So to generalize the use case, when I want to attach an event to a
child element or an element linked by any other mean to the element
having that class, I can't
Blanchard, Todd wrote:
Any markup that causes a browser to automatically clone a node will
be non-conformant and will be flagged as erroneous by a validator.
You are assuming that validators run javascript - they generally
don't.
I'm well aware that validators don't run JavaScript and I'm ta
>Any markup that causes a browser to automatically clone a node will be
>non-conformant and
>will be flagged as erroneous by a validator.
You are assuming that validators run javascript - they generally don't. (I'm
hoping to add it to Scrutinizer http://www.blackbagops.net/seaside/html ) but
t
On 2/3/06, Michel Fortin <[EMAIL PROTECTED]> wrote:
> Le 2006-02-03 à 09:30, Jim Ley a écrit :
> So to generalize the use case, when I want to attach an event to a
> child element or an element linked by any other mean to the element
> having that class, I can't use addEventListenerToClass.
So thi
Le 2006-02-03 à 09:30, Jim Ley a écrit :
Yes, but they're all using it to attach events to every one of the
class, which is why you have to look at use cases, the reason they're
doing it is not because getElementsByClassName is missing, but because
addEventListenerToClass or -moz-binding etc. ar
On 2/3/06, Gervase Markham <[EMAIL PROTECTED]> wrote:
> Jim Ley wrote:
> As an aside, I'd be interested in hearing about any JavaScript-less
> methods (that don't involve marking up every instance of the word; this
> doesn't work, as some are e.g. in href attributes.)
I was imaging your build envi
Jim Ley wrote:
> Er, no the use case people have is that they want everything that has
> class X to respond to a particular event, if you model that with
> getElementsByClassName then you cannot change a class on an element
> and have it respond, without re-running the attachment, and manage the
>
On 2/3/06, Gervase Markham <[EMAIL PROTECTED]> wrote:
> Jim Ley wrote:
> > Yes, but they're all using it to attach events to every one of the
> > class, which is why you have to look at use cases, the reason they're
> > doing it is not because getElementsByClassName is missing, but because
> > addE
Jim Ley wrote:
> Yes, but they're all using it to attach events to every one of the
> class, which is why you have to look at use cases, the reason they're
> doing it is not because getElementsByClassName is missing, but because
> addEventListenerToClass or -moz-binding etc. are missing.
But why i
Jim Ley wrote:
On 2/3/06, Gervase Markham <[EMAIL PROTECTED]> wrote:
Jim Ley wrote:
the document of course shows no use cases at all.
Is there some doubt that the ability to tag an arbitrary set of elements
and later easily get an array of those elements is a useful feature for
web developm
On 2/3/06, Gervase Markham <[EMAIL PROTECTED]> wrote:
> Jim Ley wrote:
> > the document of course shows no use cases at all.
>
> Is there some doubt that the ability to tag an arbitrary set of elements
> and later easily get an array of those elements is a useful feature for
> web development?
I'
Lachlan Hunt wrote:
> Ric Hardacre wrote:
>> Gervase Markham wrote:
>>> If you have:
>>>
>>> Fred
>>> Barney
>>> Wilma
>>>
>>> which should be picked up by getElementsByClassName("foo bar")?
>>
>> this also raises the possibility of some confusion as the order of
inheritance is important:
>>
>
Jim Ley wrote:
>> I know nothing of this "attaching events to a class name" of which you
>> speak. Can you give me a reference to a document or proposal describing it?
>
> It's the one use case described in this mailing list,
>
> See e.g.
> http://listserver.dreamhost.com/pipermail/whatwg-whatwg
On 2/3/06, Gervase Markham <[EMAIL PROTECTED]> wrote:
> Jim Ley wrote:
> > Rather than talk about technical details, can be talk about the actual
> > use cases please, working groups keep on creating things which need
> > implementing, testing etc. without once giving the use case. This
> > thread
Ric Hardacre wrote:
Gervase Markham wrote:
If you have:
Fred
Barney
Wilma
which should be picked up by getElementsByClassName("foo bar")?
this also raises the possibility of some confusion as the order of
inheritance is important:
foo
{
color: red;
}
bar
{
color: blue;
}
in the qu
On Fri, 03 Feb 2006 15:39:26 +0200, Gervase Markham <[EMAIL PROTECTED]>
wrote:
ROBO Design wrote:
<...>
Well, not according to the current spec, which says:
1. Should it return *all* elements which have *all* the class names
wanted?
this one. Of course, you may disagree with the spec.
On Fri, 03 Feb 2006 15:31:37 +0200, Ric Hardacre <[EMAIL PROTECTED]>
wrote:
this also raises the possibility of some confusion as the order of
inheritance is important:
foo
{
color: red;
}
bar
{
color: blue;
}
in the quoted example Fred and Wilma would be blue and barney red. so
ROBO Design wrote:
> I believe there's some disagreement on what is this function supposed to
> do.
Well, not according to the current spec, which says:
> 1. Should it return *all* elements which have *all* the class names wanted?
this one. Of course, you may disagree with the spec.
> 4. Should
On Fri, 03 Feb 2006 15:24:19 +0200, Shadow2531 <[EMAIL PROTECTED]>
wrote:
Do we need to be able to pass an array of arbitrary classnames?
burnout426
Yes.
--
http://www.robodesign.ro
ROBO Design - We bring you the future
On Fri, 03 Feb 2006 14:34:14 +0200, Gervase Markham <[EMAIL PROTECTED]>
wrote:
Shadow2531 wrote:
<...>
This seems like a sensible change. Call it getElementsByClassNames()
would make it obvious that if you supply multiple class names, you get
only elements with all those names. And it would
Jim Ley wrote:
> Rather than talk about technical details, can be talk about the actual
> use cases please, working groups keep on creating things which need
> implementing, testing etc. without once giving the use case. This
> thread is now 21 messages old and there's not one use case which is
>
On 2/3/06, Gervase Markham <[EMAIL PROTECTED]> wrote:
> This seems like a sensible change. Call it getElementsByClassNames()
> would make it obvious that if you supply multiple class names, you get
> only elements with all those names. And it would be a reasonably obvious
> reduction that if you ju
Gervase Markham wrote:
> Brad Fults wrote:
>> I see this is still an open issue[1]. Is this now implemented as #1
>> (space-delimited class names to match)?
>>
>> I suggest either going with the space-delimited approach (as it's
>> language-agnostic and well-defined at least) or with Aankhen's
>
On 2/3/06, Gervase Markham <[EMAIL PROTECTED]> wrote:
> This seems like a sensible change. Call it getElementsByClassNames()
> would make it obvious that if you supply multiple class names, you get
> only elements with all those names. And it would be a reasonably obvious
> reduction that if you ju
Shadow2531 wrote:
> O.K. Then, it should be getElementByClassName*s*() where you have
> have 1 or more classname arguments. If you pass more than 1 class
> name, both class names have to be present in the classname attribute
> for the element to match.
This seems like a sensible change. Call it
On 2/3/06, Shadow2531 <[EMAIL PROTECTED]> wrote:
> O.K. Then, it should be getElementByClassName*s*() where you have
> have 1 or more classname arguments. If you pass more than 1 class
> name, both class names have to be present in the classname attribute
> for the element to match.
I just to be
On 2/3/06, Gervase Markham <[EMAIL PROTECTED]> wrote:
> Shadow2531 wrote:
> > I just threw them together as a proof of concept, but I have no doubt
> > that the class attribute value should be a space separated list of
> > classnames and the getElementByClassName function should split up the
> > cl
Gervase Markham wrote:
Lachlan Hunt wrote:
Errors caused by the result of duplicate IDs either in the markup or
indirectly as a result of badly nested elements can be fixed by a quick
visit to the validator (or other conformance tool) or by making use of
any or all of those tools I mentioned abo
Shadow2531 wrote:
> I just threw them together as a proof of concept, but I have no doubt
> that the class attribute value should be a space separated list of
> classnames and the getElementByClassName function should split up the
> class attribute value into an array and then search for the class
On 2/3/06, Gervase Markham <[EMAIL PROTECTED]> wrote:
> Musing...
>
> If you have:
>
> Fred
> Barney
> Wilma
>
> which should be picked up by getElementsByClassName("foo bar")?
>
> In the "string split" mode, it would pick up all three. However, I
> suggest that designers might be misled by this in
On Fri, 03 Feb 2006 10:48:47 +0200, Gervase Markham <[EMAIL PROTECTED]>
wrote:
Brad Fults wrote:
<...>
Musing...
If you have:
Fred
Barney
Wilma
which should be picked up by getElementsByClassName("foo bar")?
In the "string split" mode, it would pick up all three. However, I
suggest that
Simon Pieters wrote:
> Browsers could mark all errors as red in view source. In Firefox you can
> select a piece of text and view selection source, which will bring up
> the serialized DOM.
They could (at least, as far as I understand the issue), for XHTML at
least (not HTML5), if they wanted to
Hi,
From: Gervase Markham <[EMAIL PROTECTED]>
It's much harder to spot them when they are dynamically generated by
e.g. a cloneNode operation. You can't submit your browser's DOM tree to
the validator...
Browsers could mark all errors as red in view source. In Firefox you can
select a piece o
Lachlan Hunt wrote:
> Errors caused by the result of duplicate IDs either in the markup or
> indirectly as a result of badly nested elements can be fixed by a quick
> visit to the validator (or other conformance tool) or by making use of
> any or all of those tools I mentioned above.
It's much har
Brad Fults wrote:
> I see this is still an open issue[1]. Is this now implemented as #1
> (space-delimited class names to match)?
>
> I suggest either going with the space-delimited approach (as it's
> language-agnostic and well-defined at least) or with Aankhen's
> suggestion of a single array ar
50 matches
Mail list logo