Previous Message
Next Message

Re: [css-d] Divergence between compliant browsers

Sent by Chris Casciano on 29 January 2002 13:01

on 1/29/02 11:07 AM, Jeffrey Zeldman at [EMAIL-REMOVED] wrote:

> If clients do not permit designers and developers to go back into
> existing sites and alter their Style Sheets to accommodate the way
> Mozilla/NN6 now renders table-based layouts, will users think
> Mozilla/NN6 is "broken?" If so, will this decrease user adoption of
> Mozilla and its derivatives, thus driving even more users to IE? (And
> what impact would such a result have on the future of standards
> compliance across all browsers?)

Well Jeffrey, putting my practical hat on I pose the following question:

Which will come first: The adoption of Gecko based (or other engine with
similar interpretations of the spec) to a point where it is great enough for
it to matter -or- the next redesign of your client's site.

If the current slow adoption of Mozilla continues, and from my own
experience in the field I would have a hard time thinking that your clients
site wouldn't have some major work done on it anyway. Mozilla has been
stable enough to be in the list of platforms to QA a site list for what,
about a year now? Unless AOL decides to switch their customers over to NN6 I
can't see adoption increasing very quickly anytime soon - not before Moz 1.0
- and we'll see if this current rate changes after that. So as much as I'd
like not to think so, a case can be made for ignoring Moz for some time

Now I wouldn't say companies redesign every year, but how long do they go
without major reconstructive surgery? Most of my clients are on their second
site in 2 or 3 years, with the caveat that their first site usually wasn't
up to par by any standards.

So is it reasonable to think that in most cases issues like this inline
image one will be resolved themselves before its a real issue?
> I also worry that it may negatively impact the already-slow adoption
> of Mozilla/NN6, and could convince some clients and developers that
> web standards are unnecessarily complicated and more trouble than
> they're worth.

I share the concern on the build side, but I'm not sure any of this will
have an impact on user adoption.

Consider OmniWeb and its adoption the OSX community. While this may be a
specialized community much like the Mozilla community is it does further the
point that user priorities are a lot different then developer & client
priorities. While I've been quite horrified by what I've seen each time I've
tried a "sneak peak" the browser continues to gain users for reasons
entirely other then its rendering engine. So unless this divergence of
<q>compliant</q> browsers causes some functionality to break I don't think
it will have too much effect on the user/visitor side of the equation.

Now, I don't want to sound like I'm dismissing your concerns here. I
interact with many web folks every day who are in the throw of deciding if
they should learn css or support moz or just scrap it all and use flash.
Myself, I'm also frustrated with the gap I see in CSS support between IE/PC
& most other browsers I'd consider current (more so the few advances from
ie5.5 to ie6 really bothers me).

So while I share many of these concerns with you I can't say that I've ever
gotten truly concerned about them.

Chris Casciano                  home >>
                                words >
[EMAIL-REMOVED]       fun >>>
Previous Message
Next Message

Message thread:

Possibly related: