I completely agree regarding Mozilla -- typically when I encounter an error, I blame the site designers and move along. Since I spend most of my time developing sites, I generally know what things are Mozilla errors, and what was just poor design.
I definitely think that some sort of "rip" (I can't justify calling it a patch, since we're really doing the exact opposite) for Mozilla to conver IE-specific garbage into standards-compliant code would be great. The biggest argument I hear from people against using Mozilla as their primary browser is that there are "so many sites that it doesn't work with." (In my own experience, that number is really not so large, but anyway...) So any opportunity to refute that argument could go a long way to breaking Microsoft's IE monopoly.
Slashdot Mirror
I completely agree regarding Mozilla -- typically when I encounter an error, I blame the site designers and move along. Since I spend most of my time developing sites, I generally know what things are Mozilla errors, and what was just poor design.
I definitely think that some sort of "rip" (I can't justify calling it a patch, since we're really doing the exact opposite) for Mozilla to conver IE-specific garbage into standards-compliant code would be great. The biggest argument I hear from people against using Mozilla as their primary browser is that there are "so many sites that it doesn't work with." (In my own experience, that number is really not so large, but anyway...) So any opportunity to refute that argument could go a long way to breaking Microsoft's IE monopoly.