Hi Andrew - Thanks for bringing this over to email...
On Wed, Feb 20, 2008 at 11:31 AM, Andrew Robinson <[EMAIL PROTECTED]> wrote: > I still think that a custom DOCTYPE should be provided. With XHTML, to > be completely specification compliant, the HTML page ought to pass DTD > validation. This means that renderers and JavaScript that add custom > attributes onto elements are invalid and should not be used. On the > other hand, making a custom DTD that defines the extra attributes is > legal. I am a big fan of fixing our expando validation problems by taking advantage of xhtml namespaced attributes. However, my feeling is that forcing the page author/app developer to specify a custom dtd which covers our internal expando use is not the best solution. Since the RenderKit/Renderers have the knowledge of which expandos are used, I would prefer to see the RenderKit produce the appropriate doctype/dtd. So, actually, I see this as another reason why custom dtds may be a bad thing, since this might interfere with the RenderKit's ability to provide the correct dtd. Perhaps we should open up a JIRA for the expando validity issue? > The downside to this is that I am not sure browsers really > support custom DTDs. Does anyone know from experience? I haven't played around with this myself, but wanted to mention that WAI-ARIA's accessible state mechanism relies on namespaced expandos: http://www.w3.org/TR/wai-aria/ So we are not in bad company if we go this route, though I believe this relies on Xhtml 1.1 modularization, which might not quite be there yet in terms of browser support. > > BTW, just curious... Anyone know whether the Trinidad renderers/skins > actually behave well in quirks mode? I think we should verify this before > exposing a quirks mode switch. > > I am using IE6 and IE7 in quirks mode and firefox in standards mode by > extending the DocumentRenderer for a project, and although I have only > used a small portion of the components, it is all working. On > occasion, I have to add tweaks to the standard skin in my custom skin. This makes me wonder whether it is a goal of Trinidad to generally support quirks mode operation across all components (without requiring skin tweaking). If so, I can see exposing a switch to make it easy to switch into quirks mode. If not, I would be concerned that this might be opening up a potentially large can of worms. At a minimum before exposing a quirks mode switch I would think we should test each component in quirks mode to see how close we are to cleanly supporting this. In my ideal world, we leave quirks mode behind, but of course I realize that the web isn't always necessarily my ideal world. :-) Andy
