Hi all. logfile-guester for a day says:
The link to my page you are citing is ideed a long standing annoyance in pixel perfect designs. But, it so happens that they are currently working very hard on this one (https://bugzilla.mozilla.org/show_bug.c … 77805#c105), and it will take its time as they have to fix a deep nested major thing with a lot of sideeffects (as I understand it, if at all).
I agree its hard to realize that, i.e., a reported CSS specification violation bug by myself, say, for Opera8beta1, is still not fixed in Opera8.01.
Must be the same feeling for a bug reporter in any other browser that allows and read a bug report sent from mortals. In this very moment you send it, you think you are part of the community, the open source and so on, but with the next release not being fixed, you can get easily the feeling that they "don't bloody fix it", like you've said.
On the other hand, listen to what they do every hour, every day: http://forums.mozillazine.org/viewtopic.php?t=265173
so many bugs fixed per day!
Reporting bugs is frustrating for the reporter, but beneficial in the sum for all, I hope.
Today, most influential Web Designers code for FF/Op/Saf etc and then debug for IE. No log stat gives you this information. Stats talk about the past and lie about the future. The other day, I've heard Safari gets a good screenreader. For free. Web standards folks have driven this.
In the end, I think we'll have some good, reliable, standards based, community-driven Browsers with the respect from designers and users. They might differ in some acessibility aspects. It's not important which of them hits the Acid2 line for the public. They all will make it in the near future. The bugfixes made for this goal will be partly beneficial, yes, and the rest is public relation, and we can be happy about good PR that will help spread good browsers.
Thanks.