- From: <bugzilla@wiggum.w3.org>
- Date: Thu, 26 Nov 2009 03:59:48 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8381
James Williams <jgwilliams@mindspring.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jgwilliams@mindspring.com
Summary|I greatly appreciate the |I greatly appreciate the
|addition of custom attribute|addition of custom user
|values, but I take strong |attribute values, but take
|exception to the particular |strong exception to the
|notation. In reality, HTML |particular notation.
|5 is providing just one |
|attribute named "data |
Summary|" which is quite acceptale |
|because attribute values may|
|be structured. W |
--- Comment #1 from James Williams <jgwilliams@mindspring.com> 2009-11-26 03:59:48 ---
I use custom attributes all the time, debugging them in MSIE and then compiling
them into legitimate but unreadable HTML in order to get along with Firefox. I
also make heavy use custom css attributes and would appreciate having the two
problems solved compatibly. Here's a sample of my work that is fully
acceptable to MSIE, but that must be "compiled" for Firefox:
.cls-gray {
color: #809080;
nskin: skin-gray;
placement: source-line;
active: { font-variant: small-caps }
}
...............
<span class="cls-gray" nref="#termDefinition"
style="placement: note">term definition</span>
Using the one-name-is-enough principle, this could easily be rewritten as
.u { cls-gray: {
color: #809080;
nskin: skin-gray;
placement: source-line;
active: { font-variant: small-caps }
}
}
...............
<span class="cls-gray" u.nref="#termDefinition"
style="u.placement: note">term definition</span>
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Thursday, 26 November 2009 03:59:50 UTC