Jough wrote:
This subject has probably risen more times than one can count on their fingers, but I have been unable to find the argument online. What, exactly, is the idea behind keeping the attributes of ‘rows’ and ‘cols’ a requirement of a textarea in XHTML 1.0? It seems to me that these values reflect formatting rather than valid information.
I agree that they smack of presentational. The same goes for the size attribute in text inputs. While maxlength can be argued as being a property that describes the nature of an input, size/rows/cols seem to be solely concerned with how the input/textarea will be presented. I usually tend to omit them from my XHTML altogether and rely on CSS instead. Even in XHTML 1.1's forms modules they're still present.
And speaking of XHTML 1.0, I was surprised to also find a lot of presentational attributes still left in the table-related elements (table, tr, th, td, col etc), even in strict. Surely width, border, cellspacing, cellpadding, valign, halign could have been expunged from strict?
In short, XHTML isn't as devoid of presentational stuff as I first believed myself.
P -- Patrick H. Lauke __________________________________________________________ re·dux (adj.): brought back; returned. used postpositively [latin : re-, re- + dux, leader; see duke.] www.splintered.co.uk | www.photographia.co.uk http://redux.deviantart.com __________________________________________________________ Web Standards Project (WaSP) Accessibility Task Force http://webstandards.org/ __________________________________________________________ ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: [EMAIL PROTECTED] *******************************************************************
