PDA

View Full Version : Re:safari



Steve Raizen
2003-11-20, 12:43
I have the same problem trying to view the server in either I.E., or Safari 1.0.

Using 10.2.8. on a G4 350. Everything worked fine on 4.2.6.

Steve


On Thu, 20 Nov 2003 11:33:37 -0800 (PST), discuss-request (AT) lists (DOT) slimdevices.com wrote:
> On Nov 20, 2003, at 9:48 AM, Rob Funk wrote:
>
>
>>> I just dont have any easy way to test
>>> or debug with Safari.
>>>
>>
>> Doesn't Safari use the same rendering engine as Konqueror? Try a
>> Linux box with KDE.
>>
>
> That might help, but with the problem of having the playlist not
> redraw I am seeing it in Safari, but not in Omniweb which uses the
> same rendering engine. It could be that Safari is using a more
> recent build, or there is a bug in Safari that won't show up in
> other browsers based on that engine.

Kevin Deane-Freeman
2003-11-20, 13:02
Quoting Steve Raizen <sraizen (AT) cityxpress (DOT) com>:

> I have the same problem trying to view the server in either I.E., or Safari
> 1.0.
>
> Using 10.2.8. on a G4 350. Everything worked fine on 4.2.6.
>
> Steve
There are two "problems" actualy. However, IE hasn't been reported as being
problematic. Are you referring to the slowdown, or the blank frames?

Try reducing the number of items displayed on a page, from the server interface
settings. You can also increase the refresh from 30 seconds to something longer
to give it more time to load. The amount of information in the playlist can
sometimes take time to load.

-kdf



> On Thu, 20 Nov 2003 11:33:37 -0800 (PST),
> discuss-request (AT) lists (DOT) slimdevices.com wrote:
> > On Nov 20, 2003, at 9:48 AM, Rob Funk wrote:
> >
> >
> >>> I just dont have any easy way to test
> >>> or debug with Safari.
> >>>
> >>
> >> Doesn't Safari use the same rendering engine as Konqueror? Try a
> >> Linux box with KDE.
> >>
> >
> > That might help, but with the problem of having the playlist not
> > redraw I am seeing it in Safari, but not in Omniweb which uses the
> > same rendering engine. It could be that Safari is using a more
> > recent build, or there is a bug in Safari that won't show up in
> > other browsers based on that engine.
>
>
>
>