Geoffry, I am not sure how to answer your question. I don't know if this is recommended or best practice. My issue is, I have a very large set of data (key,value) in xml format. This xml file is to be displayed in the browser and edited. So, I need to put it in a table, and put the values an input tags. Now, there's other input tags in the page. I can customize the inputs the way I like using css. However, the tags for the fields to be edited are text boxes. And these text boxes input can be generated in html without giving the field type. While other inputs need type. So what I wanted is to format the text boxes, but not the buttons or other inputs. I know I can add a class attribute for anything I want, but considering the size of the file, and the amount of data, this will increase the download time. Now that I tested it and completed the generation of the html using XSLT, I don't find it too bad. And I can happily live with it.
The idea of having a selector that selects an element without a specific attribute came from xpath. I work sometimes with xslt, and I find it very handy, and wondered if there's some similar functionality in CSS. For example in xpath you can do this (select="a_tag[not(@attr)]) and this will select the element called a_tag that does not have attribute "attr" set. Any way, my problem is resolved. Thank you. Geoffrey Hoffman wrote: > Is this a 'best practice' or is it recommended for inclusion in future RFCs? > I'm familiar with the idea of having exactly one id="unique" per page, but > H1? I always assumed that on a news site, for example, every headline would > be an H1, whereas every subhead would be an H2. I realize there's really no > difference in using H2 for every headline and H3 for subheads, I just > haven't set up my news-related pages that way. > > > On Thu, May 29, 2008 at 1:02 AM, Jukka K. Korpela <[EMAIL PROTECTED]> > wrote, in part: > > >> As others have noted, the h1 element is not a good example, since >> normally there is (or should be) just one h1 element per page. >> >> >> > ______________________________________________________________________ > css-discuss [EMAIL PROTECTED] > http://www.css-discuss.org/mailman/listinfo/css-d > List wiki/FAQ -- http://css-discuss.incutio.com/ > List policies -- http://css-discuss.org/policies.html > Supported by evolt.org -- http://www.evolt.org/help_support_evolt/ > > ______________________________________________________________________ css-discuss [EMAIL PROTECTED] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
