Daemach schrieb:
Thanks for the info on the metadata plugin.
Make sure to avoid any spaces... is exactly the kind of gotcha that
makes using classes as a data repository so troublesome. While it is
technically possible, mixing data types inside an attribute just feels like
a bad practice to
Daemach schrieb:
Your faith in Microsoft is certainly admirable, but the very fact that we're
talking about storing 2 kinds of information in a single attribute is cause
for concern isn't it? Thinking about the way parsers work in general, an
extra attribute in an element seems less likely to
Ⓙⓐⓚⓔ schrieb:
have you ever made a dtd that the validator likes? I gave up on that a
while back!
good luck!
Yes, unless you don't use *real* xml/xhtml there's not a real chance to
have a validator ever use your specified dtd. so the whole thing is kind
of theoretical.
-- klaus
My main issue, I think, is that I don't like the idea of mixing 2 different
types of data in one attribute. I like keeping everything separated, but
that's just me ;)
Klaus Hartl wrote:
Ⓙⓐⓚⓔ schrieb:
I think there is no risk! classes are ours to use (or abuse)... no
sane (not even IE)
Daemach schrieb:
Actually I think I may just modify the validator code to read out of a custom
expando. It would be nice to be able to pass the attribute name to the
validator engine directly though...
Jorn? ==(sorry - I don't know how to do the fancy o ;)
Heh, . Just copypaste the
Thanks for the info on the metadata plugin.
Make sure to avoid any spaces... is exactly the kind of gotcha that
makes using classes as a data repository so troublesome. While it is
technically possible, mixing data types inside an attribute just feels like
a bad practice to me.
Jörn
Daemach schrieb:
-- If I add metadata to a class attribute, I risk messing with CSS -
classes are for styles.
That is a common misunderstanding. Consider the HTML spec:
The class attribute has several roles in HTML:
* As a style sheet selector (when an author wishes to assign style
call me weird, but I like mixing the 2 types of classes , and often
use them together, with a single class.
On 3/3/07, Klaus Hartl [EMAIL PROTECTED] wrote:
Daemach schrieb:
-- If I add metadata to a class attribute, I risk messing with CSS -
classes are for styles.
That is a common
Well of course we all know that every browser follows the w3 recommendations
rigidly and without compromise, so let me put this another way:
Knowing that some browsers suck more than others (*cough* IE *cough*), is
there less risk in the browser misinterpreting non-style information in an
I think there is no risk! classes are ours to use (or abuse)... no
sane (not even IE) browser would co-opt classes from the masses!
On 3/3/07, Daemach [EMAIL PROTECTED] wrote:
Well of course we all know that every browser follows the w3 recommendations
rigidly and without compromise, so let me
I'm quoting Mike Alsup from the jQuery 1.1.2 thread, which I thought did a
good job relating to this question:
Based on this info, I feel totally safe using it. I can't even think of a
reason to use objects in this way, but I am not that complex. :)
*That's correct. It's safe to store
after reading this thread I feel comfortable using my own
'expando'/'extendo' attributes again, and using classes too!
but classes are the only way to pass the validators! If you are
horribly concerned with possible interaction with css classes, you
could remove the javascript class with jquery,
Actually I think I may just modify the validator code to read out of a custom
expando. It would be nice to be able to pass the attribute name to the
validator engine directly though...
Jorn? ==(sorry - I don't know how to do the fancy o ;)
Ⓙⓐⓚⓔ wrote:
after reading this thread I feel
have you ever made a dtd that the validator likes? I gave up on that a
while back!
good luck!
On 3/3/07, Daemach [EMAIL PROTECTED] wrote:
Actually I think I may just modify the validator code to read out of a custom
expando. It would be nice to be able to pass the attribute name to the
This is more philosophical than anything, but I was just looking over the
metadata, metaobjects and validation plugin and I keep coming back to a
question of what is the least of all the evils.
-- If I add metadata to a class attribute, I risk messing with CSS -
classes are for styles.
-- If I
15 matches
Mail list logo
