Re: Microsoft MVPs

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Kevin Spencer (kevin_at_DIESPAMMERSDIEtakempis.com)
Date: 03/10/05


Date: Thu, 10 Mar 2005 08:27:06 -0500

Let me put it this way. How come you can view the same web page in different
browsers? Because they all use HTML. They don't each use their own "flavor"
of HTML. They adhere to a standard ("recommendation" from Tom's point of
view). If they didn't, you would need a proprietary program to view each
different web site. Much the same as needing a proprietary program to open a
Word document.

It's all about usability. Whether you acknowledge the need for standards
("recommendations" or not, browser manufacturers do, and they try to adhere
to them (whatever "they" are). Usability and cross-platform compatibility
are achieved in Internet technologies by standards that various software
companies try to adhere to.

If it wasn't fort "standards" there would be no JavaScript, no HTML, not
even TCP/IP. And all of our lives would be a lot simpler, since we wouldn't
have to write apps that can talk across networks.

-- 
HTH,
Kevin Spencer
Microsoft MVP
.Net Developer
What You Seek Is What You Get.
"David Baxter" <spam-me@junkmail.com> wrote in message 
news:%23oxzOrTJFHA.576@TK2MSFTNGP15.phx.gbl...
> Why "must" they be reckoned with? With the exception of web designers,
> more than 90% of the world is still using browsers which either don't
> care or don't support those recommendations.
>
> I keep hearing dire warnings along the lines of "if you don't conform,
> in the near future your visitors won't be able to view your pages" but I
> don't see it happening...
>
> "Kevin Spencer" <kevin@DIESPAMMERSDIEtakempis.com> wrote in message
> news:eRIA6WNJFHA.2956@TK2MSFTNGP12.phx.gbl...
>> You call them recommendations. I call them standards. No matter what
> name
>> you give to them, they exist, and must be reckoned with.
>>
>> -- 
>> HTH,
>>
>> Kevin Spencer
>> Microsoft MVP
>> .Net Developer
>> What You Seek Is What You Get.
>>
>> "Thomas A. Rowe" <tarowe@mvps.org> wrote in message
>> news:e%233zsJNJFHA.3484@TK2MSFTNGP12.phx.gbl...
>> > If there were "standards", then every browser would support the same
>> > features/functions in the same manner and we wouldn't have to be
> concerned
>> > at all about browsers, just building great web sites.
>> >
>> > BTW: My solution is to not use CSS for positioning, etc. and to
> stick
>> > fairly close to the HTML 3.2 recommendations which are supported by
> all
>> > current browsers.
>> >
>> > -- 
>> > ==============================================
>> > Thomas A. Rowe (Microsoft MVP - FrontPage)
>> > WEBMASTER Resources(tm)
>> > http://www.ycoln-resources.com
>> > FrontPage Resources, WebCircle, MS KB Quick Links, etc.
>> > ==============================================
>> > To assist you in getting the best answers for FrontPage support see:
>> > http://www.net-sites.com/sitebuilder/newsgroups.asp
>> >
>> > "Al Sparber" <adSTRApmin@projectseven.com> wrote in message
>> > news:uj%23TN2MJFHA.1304@TK2MSFTNGP09.phx.gbl...
>> >> "Thomas A. Rowe" <tarowe@mvps.org> wrote in message
>> >> news:O8MV9cMJFHA.3832@TK2MSFTNGP12.phx.gbl...
>> >>> There are no standards, just recommendations.
>> >>
>> >> That's technically true. But it's not an answer that provides a
> solution
>> >> :-)
>> >>
>> >> CSS2.1 is a finished specification. IE6 supports about 90% of the
>> >> specification. Newer browsers support about 98%. How is a web
> developer
>> >> supposed to use CSS unless he knows which browsers support which
>> >> properties? Is there a constructive solution anywhere in this
> thread?
>> >>
>> >> Tune in to Microsoft's Channel 9 site to see what Microsoft
> developers
>> >> and engineers think about standards. I think you'll be surprised
> that
>> >> they are not only for them, they are also part of the W3C.
>> >>
>> >> I would bet that IE7 (or the version that ships with Longhorn) will
> have
>> >> terrific support for CSS2.1 "recommendations". Not for any other
> reason
>> >> than to give web developers the tools they need to use CSS and have
> sites
>> >> be as stable on IE as they are on Firefox.
>> >>
>> >> I'd put some money on that :-)
>> >>
>> >>
>> >> -- 
>> >> Al Sparber
>> >> PVII
>> >> http://www.projectseven.com
>> >>
>> >> "Designing with CSS is sometimes like barreling down a crumbling
> mountain
>> >> road at 90 miles per hour secure in the knowledge that repairs are
>> >> scheduled for next Tuesday".
>> >>
>> >>
>> >
>> >
>>
>>
>
> 


Relevant Pages

  • Re: iceweasel based on firefox 6.0 for squeeze
    ... the Canvas element has been supported by Apple's Webkit since 2004. ... HTML 5 is not a finalised standard *yet*. ... It will never be fully supported by all browsers - even when ... then you can start testing browsers for HTML 5 support. ...
    (Debian-User)
  • Re: Microsoft MVPs
    ... > FrontPage Resources, WebCircle, MS KB Quick Links, etc. ... I call them standards. ... then every browser would support the same ... >>> concerned at all about browsers, ...
    (microsoft.public.frontpage.client)
  • Re: why a different tag for SVG images?
    ... Way back, for example, some browsers supported ... support all conceivable formats. ... really the business of the HTML authoring group. ...
    (comp.infosystems.www.authoring.html)
  • Re: Microsoft MVPs
    ... You call them recommendations. ... I call them standards. ... then every browser would support the same ... > at all about browsers, ...
    (microsoft.public.frontpage.client)
  • Re: Form action= ?
    ... And it's the other way around: DTDs in HTML ... Browsers tend to be much more permissive than ... I can, however imagine people getting ahead of slow standards development, and making "semi-educated" assumptions. ...
    (alt.html)