On Tue, Aug 5, 2008 at 2:42 AM, Simetrical <simetrical@gmail.com> wrote: > That's not true. For instance, latest Gecko does not support @page, > display: run-in, white-space: pre-line, and probably other CSS2.1 > features. I don't think any UA "fully supports" CSS2 or CSS2.1 yet. The *very* latest Gecko (i.e. trunk) does support pre-line :-). > The extra complexity is trivial even in an absolute sense, and even > more so when you take into account that it potentially replaces a huge > array of selector hacks and JavaScript. (And selector hacks become > even harder to maintain as browsers become more standardized.) It > doesn't get around issues of *old* buggy browsers, but it will help to > get around issues of *new* buggy browsers. It's idealistic to suppose > that there won't be any ever. > Indeed. Rob -- "He was pierced for our transgressions, he was crushed for our iniquities; the punishment that brought us peace was upon him, and by his wounds we are healed. We all, like sheep, have gone astray, each of us has turned to his own way; and the LORD has laid on him the iniquity of us all." [Isaiah 53:5-6]
Received on Tuesday, 5 August 2008 00:54:08 UTC