Simpler for who? If we assume hypothetically for a moment that it's reasonable to allow developers to specify "custom" attributes, then it's obviously easier for them to just specify the syntax which adds the custom attributes, as opposed to having them do the work of defining a subclass and changing the TLD.
I've always been sympathetic to the goal of enforcing the HTML standard, particularly for "internet" applications, as opposed to "intranet" applications. However, when it comes to supporting intranet applications, a more effective approach might be the pragmatic one. -----Original Message----- From: Joe Germuska [mailto:[EMAIL PROTECTED] Sent: Monday, February 09, 2004 9:52 AM To: Struts Developers List Subject: Re: Browser-specific attrs for html tags (was: [Bug 26795]) At 9:28 AM -0800 2/9/04, Hubert Rabago wrote: >This probably won't be the last request for an attribute which turns >out to be browser specific. Perhaps the html taglib can include some >mechanism to allow developers to add other attributes. You can always subclass the tag and change the TLD file. This seems like a much simpler solution to me. Joe -- Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "Imagine if every Thursday your shoes exploded if you tied them the usual way. This happens to us all the time with computers, and nobody thinks of complaining." -- Jef Raskin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
