> 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, I would love to say that we do not support quirks mode in Trinidad. Since the code always uses standards mode now and a developer has to "hack" Trinidad to get into quirks mode, then it would not break ppl. by requiring standards mode. The one valid argument for quirks mode is the lack of support in IE for heights. In IE quirks mode (firefox works in either mode), layout can be done with TABLE elements to be able to fill the screen. CSS2 is not powerful enough for this unfortunately. <table style="height: 100%; width: 100%; table-layout: fixed;"> <tbody> <tr style="height: 100px;"><td/></tr> <tr style="height: 100%;"><td/></tr> </tbody> </table> Results (Q = quirks mode, S: standards mode): IE6Q, IE7Q, FFQS: Table fills the parent Second row is the table height - 100px IE6S, IE7S: Table is the parent height + 100px Second row is the height of the table's parent Basically IE drops the "height:100%" from the table if there are any heights specified on the rows or columns. If we can find a good solution around this, I am not aware of other things that only work in quirks mode that don't work as well or better in standards mode. -Andrew
