On Fri, 18 May 2007, Lachlan Hunt wrote:
Ian Hickson wrote:
In response to overwhelming feedback on this issue (especially in
blogs, forums, and mailing lists other than this one, like www-html
and public-html) I've removed the predefined classes. They're opaque
again.
The main
On Thu, 17 May 2007, Michel Fortin wrote:
Le 2007-05-17 à 12:22, Adrienne Travis a écrit :
A lot of us loved the IDEA of predefined classes, but didn't like
the idea of confusing THAT mechanism with the CSS class mechanism.
Personally, I really don't like thinking of class= exclusively
On Fri, 18 May 2007, Leif Halvard Silli wrote:
On Thu, 17 May 2007, Adrienne Travis wrote:
Is there still room for discussion regarding the /role/ attribute
with namespacing as an alternative? A lot of us loved the IDEA of
predefined classes, but didn't like the idea of confusing THAT
the start. I think the initial idea was that the class attribute would
cover the the semantics while CSS the presentation of those semantics.
The only problem is that earlier specs left those semantics undefined,
with no way to define them unambiguously
you can unambiguously define the
I'm not exactly sure what the context of this e-mail was (it seemed to be
a non-sequitur relative to its parent e-mail in the thread). It seems,
however, that it was attempting to suggest a solution without describing
the problem being solved, which makes it difficult to evaluate. I've
mostly
Is there still room for discussion regarding the /role/ attribute with
namespacing as an alternative? A lot of us loved the IDEA of
predefined classes, but didn't like the idea of confusing THAT
mechanism with the CSS class mechanism.
Adrienne
On 5/16/07, Ian Hickson [EMAIL PROTECTED] wrote:
Le 2007-05-17 à 12:22, Adrienne Travis a écrit :
A lot of us loved the IDEA of predefined classes, but didn't like
the idea of confusing THAT mechanism with the CSS class mechanism.
Personally, I really don't like thinking of class= exclusively as a
mechanism to associate styles. The fact
I understand the idea that classes were supposed to have semantics all
along -- though i don't think that idea is necessarily borne out by
the spec -- but the issue, for me, is NAMESPACING (whether formally
defined or otherwise). If i'm using class=navigation and
class=copyright (to use two
Le 2007-05-17 à 13:54, Adrienne Travis a écrit :
If we could NAMESPACE the predefined class names, that'd actually
remove ALL my objections to the idea of overloading /class/ instead of
creating a new attribute (/role/ or whatever). But unfortunately, that
totally breaks backwards-compatibility
Hello Adrienne,
I'm not sure how good or bad IE is in general at this stuff.
But I know escaping the : works in IE (for CSS)... because I did it
before. (Works in Firefox too of course.)
See ya
On 5/17/07, Adrienne Travis [EMAIL PROTECTED] wrote:
Charles,
I went and looked, and per the
Was this supposed to be on the list? I'm not sure, so I'll reply to
you personally. Feel free to forward it if you want.
Le 2007-05-17 à 16:44, Adrienne Travis a écrit :
The CSS 1 spec says that a selector CANNOT start with a dash. I find
nothing in the CSS 2 spec to overwrite that, though i
Ian Hickson wrote:
In response to overwhelming feedback on this issue (especially in blogs,
forums, and mailing lists other than this one, like www-html and
public-html) I've removed the predefined classes. They're opaque again.
The main use cases for predefined classes can mostly be dealt
On May 17, 2007, at 5:43 PM, Lachlan Hunt wrote:
Ian Hickson wrote:
In response to overwhelming feedback on this issue (especially in
blogs, forums, and mailing lists other than this one, like www-
html and public-html) I've removed the predefined classes. They're
opaque again.
The main
There are various possible solutions to replace error and warning, some
of which include the following. (This is just brainstorming, neither of
these are particularly well thought out ideas.)
1. New attn element (short for 'attention'), which is specifically for
attracting the users attention,
On 2007-05-18 00:37:53 +0200 Ian Hickson [EMAIL PROTECTED] wrote:
On Thu, 17 May 2007, Adrienne Travis wrote:
Is there still room for discussion regarding the /role/ attribute with
namespacing as an alternative? A lot of us loved the IDEA of predefined
classes, but didn't like the idea of
In response to overwhelming feedback on this issue (especially in blogs,
forums, and mailing lists other than this one, like www-html and
public-html) I've removed the predefined classes. They're opaque again.
The main use cases for predefined classes can mostly be dealt with using
some of
16 matches
Mail list logo
