Lachlan Hunt wrote:
we could introduce the edit and datetime attributes from the XHTML
2.0 draft's Edit Attributes Module [1].
I just realised that the datetime attribute from the Edit module would
clash with the proposed datetime attribute of the element [1].
e.g. What would the datetime a
- Original Message -
From: "Anne van Kesteren" <[EMAIL PROTECTED]>
To: "WHATWG" <[EMAIL PROTECTED]>
Sent: Wednesday, August 30, 2006 1:35 AM
Subject: Re: [whatwg] Lists, /, and
| On Wed, 30 Aug 2006 09:16:54 +0200, Lachlan Hunt
| <[EMAIL PROTECTED]> wrote:
| > I don't know what the inv
Le 30 août 2006 à 4:31, Anne van Kesteren a écrit :
The meaning of your markup is that you inserted and deleted some
text within each list item, not that you added or deleted a list
item like in mine. Semantically there is a difference, subtle
maybe but still there.
That depends on the de
Michel Fortin wrote:
Le 30 août 2006 à 2:49, dolphinling a écrit :
What's more, it's not backwards compatible. I would *love* it if it
were (especially because then fieldset could also go there, and
repetition template attributes wouldn't have to apply to all
elements), but current UAs turn t
On Tue, 29 Aug 2006 20:18:19 +0200, Ian Hickson <[EMAIL PROTECTED]> wrote:
This is already the case in other aspects of the API, I think.
As you pointed out some to me, not for percentage rgb color values.
I don't recall what this thread was about. Was there a change you wanted
made to the sp
Le 30 août 2006 à 2:49, dolphinling a écrit :
What's more, it's not backwards compatible. I would *love* it if it
were (especially because then fieldset could also go there, and
repetition template attributes wouldn't have to apply to all
elements), but current UAs turn text
into text.
Kornel Lesinski wrote:
>>> My current solution is:
>>>
>>
>>This can be accomplished by having elements in each individual
>> cell...
>
> Of course it can, but it bloats code a lot. You have to add several
> redundant links, add tabindex=-1 to avoid breaking keyboard navigation,
> move a
Anne van Kesteren wrote:
del { display: none }
you'll see a one-item list for my markup, while for your markup you'll
see a second, empty list item.
That could be seen as a limitation of the styling language. It has been
repeated many times on this list that styling should not be taken
On Wed, 30 Aug 2006 09:16:54 +0200, Lachlan Hunt
<[EMAIL PROTECTED]> wrote:
I don't know what the inversion attribute is supposed to mean, but the
class attribute is semantically meaningless. However, we could
introduce the edit and datetime attributes from the XHTML 2.0 draft's
Edit Attri
Ric Hardacre wrote:
Another related thought we could discuss for revision control using ins
and del is that they could do with a couple of attributes, a datetime
http://www.w3.org/TR/html401/struct/text.html#adef-datetime
and an author:
On a dull and dreary afternoon I added this text while
On Wed, 30 Aug 2006 05:51:39 +0200, Michel Fortin
<[EMAIL PROTECTED]> wrote:
The meaning of your markup is that you inserted and deleted some text
within each list item, not that you added or deleted a list item like in
mine. Semantically there is a difference, subtle maybe but still there.
Michel Fortin wrote:
> Le 29 août 2006 à 23:00, Lachlan Hunt a écrit :
>
>> Michel Fortin wrote:
>>> How can we markup removed or inserted list items? Here's a general idea:
>>>
>>> Some list item
>>> Another list item
>>>
>>
>> This can be solved by putting the ins and del ele
- Original Message -
From: "Lachlan Hunt" <[EMAIL PROTECTED]>
To: "Andrew Fedoniouk" <[EMAIL PROTECTED]>
Cc: "whatwg List" <[EMAIL PROTECTED]>
Sent: Wednesday, August 30, 2006 12:07 AM
Subject: Re: [whatwg] Fw: Lists, /, and
Andrew Fedoniouk wrote:
someListElement.select( "li:not(l
Andrew Fedoniouk wrote:
Lets forget about or as anyway this is better
Some list item
Another list item
I don't know what the inversion attribute is supposed to mean, but the
class attribute is semantically meaningless. However, we could
introduce the edit and datetime attributes fro
Andrew Fedoniouk wrote:
someListElement.select( "li:not(li li)", foo);
That selector won't work anyway, because (according to the Selectors
spec) :not() can only contain a single simple selector.
--
Lachlan Hunt
http://lachy.id.au/
15 matches
Mail list logo