Sorry for late answer, but there are my few coins on custom attributes. For XHTML solution exists many years - from the beginning of XHTML itself: XML namespaces. Define custom attributes in custom namespace, and the resulting XHTML page will be perfectly valid. Example (stripped from working system):
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd";> <html xmlns="http://www.w3.org/1999/xhtml"; xmlns:a="Ajaxify framework" xmlns:v="Form navigation and validation framework"> <head> <title>Title</title> </head> <body> <div id="content"></div> <a href="content.html" a:target="content" a:confirm="Update content?">Refresh</a> </body> </html> Works in almost any browser (IE6+, Opera 9+, Firefox 3.5+, Chrome 10+, Safari 4+ - each and every browser currently used by our developers, testers and clients), passes W3C validation. The biggest problem was escaping/not escaping semicolon in CSS selectors for different selector engines: Prototype 1.6 legacy selector and Prototype 1.7 + NWMatcher allows unescaped semicolon like $$("a[a:target]"), while Prototype 1.7 + Sizzle requires backslash $$("a[a\:target]"). -- You received this message because you are subscribed to the Google Groups "Prototype & script.aculo.us" group. To view this discussion on the web visit https://groups.google.com/d/msg/prototype-scriptaculous/-/4F_HfwnzTicJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/prototype-scriptaculous?hl=en.
