> At 03:42 PM 11/29/2007, DAVOUD TOHIDY wrote:
> >However your layout is not stable.  For the definition of layout
> >stability please see my portfolio at :
> 
> I think Davoud's response shows us why the answer to the question
posed in
> the subject is "virtually nothing."  There are too many people using
other
> browsers, and unless we're going to be creating websites to work
> specifically in Firefox, we're still going to have to work with the
lowest
> common denominator in the name of site, which has NEVER been Firefox,
in
> the name of "site stability."  Most of the compromises I've made in my
own
> web design efforts have been to account for Internet Explorer's
> inadequacies.  Only once have I had to make a change because of a
Firefox
> problem, where I found a completely valid CSS construct that crashed
the
> Gecko rendering engine (I never revisited that construct, since there
are
> always people out there who don't keep their browsers up to date, so
even
> if the bug is fixed, I don't want to be crashing the browsers of
people
> who
> don't bother keeping up to date).
> 
> That the new Firefox can pass the acid stress test is really nice, but
> since we're talking about a browser that has, depending on who you
ask,
> 5-15% of the browser market share, it really doesn't mean much to a
web
> developer that isn't willing to spite everyone who uses inferior
rendering
> engines. :)


Hey, you're preaching to the choir!

http://www.phazm.com/notes/productivity/stop-the-hate-ie6-isnt-so-bad/

I understand your point, but I disagree that it changes virtually
nothing.

While a lot of the functionality is essentially proprietary until other
browsers support it (and obsolete browsers die) FF3 still has some good
enhancements that will spur other browsers into a bit more action (not
to mention, I think FF users will upgrade to the latest much faster than
IE users)

Things like getElementsByClassName are still useful, because if you run
it with a library that supports it, it will simply speed the script up
(because it doesn't have to traverse the DOM to find all class names, it
can go directly to them) - So it is backwards compatible.

Yes, handlers for protocols like "validate:http://www.phazm.com/"; are
going to be somewhat useless for some time to come, but at least you can
do things like setting up mailto: to go to another service instead of
the users default.

For the most part, I am thinking that the enhancements made will at the
very least get some more market share for FF, and more people off IE6,
and hopefully get IE to adopt some standards.

 - Jon
______________________________________________________________________
css-discuss [EMAIL PROTECTED]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/

Reply via email to