[Ham-Mac] Safari Bug?

John E Bastin jbastin at sssnet.com
Mon Sep 12 08:53:56 EDT 2005


On Sep 12, 2005, at 1:20 AM, kd5nwa wrote:


> Interesting way of looking at it, if code that is incorrect doesn't  
> work you should change the browser not the code.
>

You change the browser capabilities to deal with the incorrect code;  
there are enough examples of this kind of incorrect code out there to  
make it a reasonable tactic, much easier than trying to change the  
sloppy habits of hundreds or thousands of Web programmers.


>
> That's the line that Microsoft has been pulling for years make  
> software that generates incorrect web pages that only their  
> browsers can display to force everyone to use their products only.
>

Not at all the same thing. Safari doesn't create Web pages, we only  
ask for it to be capable of dealing with all the different styles of  
pages out there (even ones that are coded with Front Page, although  
the page we are discussing here was not).

An incorrect HTML version declaration shouldn't invalidate the page  
in a browser, the browser should deal with all versions of HTML code,  
from the old stuff to the newest. If IE does it (remember, this page  
wasn't coded with any Microsoft-proprietary stuff), Firefox handles  
it, Opera handles it, it shouldn't be asking too much for Safari to  
handle it, as well.

73,

John E Bastin, K8AJS
jbastin at sssnet.com
http://www.qsl.net/k8ajs/



>
>
>
>
>> Nevertheless, if the page works in every other browser and even in  
>> earlier versions of Safari, then it's a Safari bug, and should be  
>> fixed by Apple.
>>
>> Send the URL to Apple and complain that it doesn't work in Safari  
>> 2.0 in Tiger, even though it worked in earlier versions. Hopefully  
>> they'll get it fixed.
>>
>> 73,
>> John E Bastin, K8AJS
>> jbastin at sssnet.com
>> http://www.qsl.net/k8ajs/
>>
>> On Sep 11, 2005, at 4:50 PM, D. J. wrote:
>>
>>
>>
>>> More loose standards.  Tightened up in later versions.
>>>
>>>
>>> On 11, Sep 2005, at 15:19, Dick Kriss, AA5VU wrote:
>>>
>>>
>>>
>>>> Very interesting that the old OS (10.2) and Safari 1.0.3 works  
>>>> but the newer
>>>> OS 10.4 and Safari 2.0.1 fail big time.
>>>>
>>>> Dick
>>>>
>>>>
>>>> On 9/11/05 12:12 PM, "John Townend" <jltownend at btinternet.com>  
>>>> wrote:
>>>>
>>>>
>>>>
>>>>> Do not wish to muddy the water and not sure what this indicates  
>>>>> but
>>>>> http://www.n4gn.com opens fine on my OSX 10.2.8 using Safari  
>>>>> 1.0.3.
>>>>> 73, John G3BBD / N3YZR
>>>>> On Sunday, Sep 11, 2005, at 13:03 Europe/London, Dick Kriss, AA5VU
>>>>> wrote:
>>>>>
>>>>>
>>>>>
>>>>>> I worked T88GG on CW and noticed the QRZ web page referred to the
>>>>>> operator's
>>>>>> home page at http://www.n4gn.com.  The page as well as
>>>>>> http://www.n4gn.com/t8 was big time hosed as displayed in my  
>>>>>> OSX 10.4
>>>>>> Safari
>>>>>> browser.  I sent Tim and note and some screen shots.   After  
>>>>>> receiving
>>>>>> his
>>>>>> reply, I tried Firefox and the page worked perfect but is  
>>>>>> still hosed
>>>>>> in
>>>>>> Safari version 2.01.
>>>>>>
>>>>>> I wonder if this is an example of a bug in Safari or if my Safari
>>>>>> preference
>>>>>> file is hosed. Any suggestions on how to get Safari to display  
>>>>>> N4GN's
>>>>>> web
>>>>>> page?
>>>>>>
>>>>>> Dick, AA5VU
>>>>>>
>>>>>> Ps: The email log check t8-log at n4gn.com with a call in the  
>>>>>> subject
>>>>>> works FB.
>>>>>>
>>>>>>
>>
>>




More information about the Ham-Mac mailing list