(In reply to Scott Trenda from comment #380)
> Once you have a
> :-moz-column() pseudo-class selector in place, couldn't you just add this
> set of rules to the internal Mozilla default stylesheet?
Scott, your remark seems to me to make a lot of sense. Pretty much.
Maybe not in the solution itself, but rather in its philosophy.
I mean, the missing parts you mentioned would need some extra programmatic approach, like linking (default, built-in) Javascript procedures to default CSS.
A few facts.
1. HTML4 documents and applications won't vanish overnight once HTML5 will be a standard. A better support to HTML4 will make the web a better place.
(In reply to Scott Trenda from comment #380)
> Once you have a
> :-moz-column() pseudo-class selector in place, couldn't you just add this
> set of rules to the internal Mozilla default stylesheet?
Scott, your remark seems to me to make a lot of sense. Pretty much.
Maybe not in the solution itself, but rather in its philosophy.
I mean, the missing parts you mentioned would need some extra programmatic approach, like linking (default, built-in) Javascript procedures to default CSS.
A few facts.
1. HTML4 documents and applications won't vanish overnight once HTML5 will be a standard. A better support to HTML4 will make the web a better place.
2. W3C standards have proven not to be bullet proof (among the most recent cases: http:// it.slashdot. org/story/ 11/10/22/ 0310230/ xml-encryption- broken- need-to- fix-w3c- standard).
3. Smart interpretation (of standards) and implementation (of browsers) in the mid- long-term are better than strict ones.
(In reply to Scott Trenda from comment #380)
> So please, godspeed on bug 371323. :)
Yes, pleeeease!