Murray
Thu Dec 01 17:11:41 CST 2005
> The way things are going, browser differences will be negligible in just
> another year or two.
Then it'll only be another 4 years or so until all older versions have been
replaced....
Generally speaking, though, I definitely agree with you - it's much more
permissive for advanced CSS layout methods now than it was even 2 years ago.
--
Murray
============
"Kevin Spencer" <kevin@DIESPAMMERSDIEtakempis.com> wrote in message
news:%230C0ros9FHA.1028@TK2MSFTNGP11.phx.gbl...
> You might want to check up on what the browser vendors have been doing in
> the past couple of years. The way things are going, browser differences
> will be negligible in just another year or two. It's good for everyone,
> and everyone has figured this out. It's not so important what the
> dictionary says. It's more important what everyone agrees to. There isn't
> a single major browser manufacturer that doesn't agree that the standards
> of the W3C, ECMA, ISO, etc, are good for everyone, and there isn't a
> single major browser manufacturer that isn't working to adhere to them.
>
> You ought to be glad about this, Tom. It is making life much easier for
> everyone in the web business!
>
> --
> HTH,
>
> Kevin Spencer
> Microsoft MVP
> .Net Developer
> If you push something hard enough,
> it will fall over.
> - Fudd's First Law of Opposition
>
> "Thomas A. Rowe" <tarowe@mvps.org> wrote in message
> news:OeY$8pr9FHA.636@TK2MSFTNGP10.phx.gbl...
>> See:
>>
>>
http://www.m-w.com/dictionary/Recommendations
>>
>>
http://www.m-w.com/dictionary/Standards
>>
>> --
>> ==============================================
>> Thomas A. Rowe (Microsoft MVP - FrontPage)
>> ==============================================
>> If you feel your current issue is a results of installing
>> a Service Pack or security update, please contact
>> Microsoft Product Support Services:
>>
http://support.microsoft.com
>> If the problem can be shown to have been caused by a
>> security update, then there is usually no charge for the call.
>> ==============================================
>>
>> "Thomas A. Rowe" <tarowe@mvps.org> wrote in message
>> news:uReZkkr9FHA.952@TK2MSFTNGP12.phx.gbl...
>>> Mainly I am concerned about version 4 and up browsers and I really do
>>> not put much stock in to the recommendation by the W3C, since they are
>>> not standards, so each browser maker can choose to follow or not follow
>>> the recommendation, which has been the case since the beginning if the
>>> public internet.
>>>
>>> --
>>> ==============================================
>>> Thomas A. Rowe (Microsoft MVP - FrontPage)
>>> ==============================================
>>> If you feel your current issue is a results of installing
>>> a Service Pack or security update, please contact
>>> Microsoft Product Support Services:
>>>
http://support.microsoft.com
>>> If the problem can be shown to have been caused by a
>>> security update, then there is usually no charge for the call.
>>> ==============================================
>>>
>>> "Kevin Spencer" <kevin@DIESPAMMERSDIEtakempis.com> wrote in message
>>> news:Ox$khfr9FHA.1572@TK2MSFTNGP10.phx.gbl...
>>>> Hi Tom,
>>>>
>>>> Your question was "Is that supported by all browsers?" Well, obviously,
>>>> the answer to that is "no." There are probably some 10-year-old
>>>> browsers out there somewhere. So, as I knew you weren't really asking
>>>> that question, I checked the W3C specification, and found that it is
>>>> supported by the HTML 4.0 spec (released in December of 1997 - 7 years
>>>> ago). The current spec is HTML 4.01. Currently, almost all browsers
>>>> support the W3C HTML 4.0 spec. So, no, it didn't answer your exact
>>>> question. But assuming that you were asking if it is supported by
>>>> almost all browsers, it did answer your question. That answer would be
>>>> "yes."
>>>>
>>>> --
>>>> HTH,
>>>>
>>>> Kevin Spencer
>>>> Microsoft MVP
>>>> .Net Developer
>>>> If you push something hard enough,
>>>> it will fall over.
>>>> - Fudd's First Law of Opposition
>>>>
>>>> "Thomas A. Rowe" <tarowe@mvps.org> wrote in message
>>>> news:O$1Jqzp9FHA.3760@TK2MSFTNGP14.phx.gbl...
>>>>> But that doesn't answer my question...
>>>>>
>>>>> --
>>>>> ==============================================
>>>>> Thomas A. Rowe (Microsoft MVP - FrontPage)
>>>>> ==============================================
>>>>> If you feel your current issue is a results of installing
>>>>> a Service Pack or security update, please contact
>>>>> Microsoft Product Support Services:
>>>>>
http://support.microsoft.com
>>>>> If the problem can be shown to have been caused by a
>>>>> security update, then there is usually no charge for the call.
>>>>> ==============================================
>>>>>
>>>>> "Kevin Spencer" <kevin@DIESPAMMERSDIEtakempis.com> wrote in message
>>>>> news:%23jiiuWp9FHA.3664@TK2MSFTNGP10.phx.gbl...
>>>>>> Hi Tom,
>>>>>>
>>>>>> It is part of the W3C HTML 4.0 specification.
>>>>>>
>>>>>> --
>>>>>> HTH,
>>>>>>
>>>>>> Kevin Spencer
>>>>>> Microsoft MVP
>>>>>> .Net Developer
>>>>>> If you push something hard enough,
>>>>>> it will fall over.
>>>>>> - Fudd's First Law of Opposition
>>>>>>
>>>>>> "Thomas A. Rowe" <tarowe@mvps.org> wrote in message
>>>>>> news:eUbw$jo9FHA.1416@TK2MSFTNGP09.phx.gbl...
>>>>>>> Is that supported by all browsers?
>>>>>>>
>>>>>>> --
>>>>>>> ==============================================
>>>>>>> Thomas A. Rowe (Microsoft MVP - FrontPage)
>>>>>>> ==============================================
>>>>>>> If you feel your current issue is a results of installing
>>>>>>> a Service Pack or security update, please contact
>>>>>>> Microsoft Product Support Services:
>>>>>>>
http://support.microsoft.com
>>>>>>> If the problem can be shown to have been caused by a
>>>>>>> security update, then there is usually no charge for the call.
>>>>>>> ==============================================
>>>>>>>
>>>>>>> "Murray" <forums@HAHAgreat-web-sights.com> wrote in message
>>>>>>> news:%23dA2YFn9FHA.1276@TK2MSFTNGP09.phx.gbl...
>>>>>>>> <input type="text" readonly="readonly" value="You cannot change
>>>>>>>> this"></input>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Murray
>>>>>>>> ============
>>>>>>>>
>>>>>>>> "Joe" <Joe@discussions.microsoft.com> wrote in message
>>>>>>>> news:691B4278-041B-4AC7-BC62-89F5F6884B81@microsoft.com...
>>>>>>>>>I am using FrontPage 2003. I have a form page to display a row of
>>>>>>>>>data from
>>>>>>>>> a database and gives the user the ability to edit some fields. I
>>>>>>>>> don't want
>>>>>>>>> them to be able to edit all of the fields. How do I change the
>>>>>>>>> properties on
>>>>>>>>> the form? I used the Database Interface Wizard to create the
>>>>>>>>> page. It
>>>>>>>>> appears that when I click the edit button and then view the source
>>>>>>>>> in IE that
>>>>>>>>> the properties of the fields are in a javascript, but I can't
>>>>>>>>> find the
>>>>>>>>> javascript anywhere to edit it.
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>
>