Forrest Corbett | 1 Dec 2003 08:03
In OS 9 that's called web stalker. I actually use it to create diagrams 
of data space to visually represent the organization of a web site 
which a user subconsciously experiences when visiting a site :o)

On Nov 28, 2003, at 5:22 PM, Mark Meredith wrote:

>
> It is my best guess that they have combined OmniGraffle with OmniWeb. 
> Just imagine your page hierarchy as a slick OmniGraffle diagram.
>
Jake Robb | 2 Dec 2003 00:53
Picon

funky rendering bug

At this page:

http://www.pcpro.co.uk/?http://www.pcpro.co.uk/news/news_story.php?id=50826

The bottom "Loading" status bar scrolled up with the content when I scrolled
the frame.  See the screenshot:

http://homepage.mac.com/jakerobb/ow.pdf

-Jake
Karl Kuehn | 2 Dec 2003 02:47
Picon

Re: funky rendering bug

	This page does indeed do a good job of exposing some bugs in the  
rendering system on OmniWeb... I was not able to get the same bug, but  
did get this one:

	http://larkost.dyndns.info/Picture3.png

	The little movement triangle on the corner of the window followed the  
content up and down when I use my scroll wheel. It was quite amusing.

		Karl Kuehn
			larkost <at> softhome.net

PS... Jake Robb... in the future please do not post screen-capture  
pdf's... If you are on MacOS 10.3, open the pdf in preview.app, and  
export to a better format, such as png. And at least use it to crop the  
image. 150 some k for an image is a bit excessive... especially for  
those of us on dial-up at home (no service here... *sigh*).

On Dec 1, 2003, at 6:53 PM, Jake Robb wrote:

> At this page:
>
> http://www.pcpro.co.uk/?http://www.pcpro.co.uk/news/news_story.php? 
> id=50826
>
> The bottom "Loading" status bar scrolled up with the content when I  
> scrolled
> the frame.  See the screenshot:
>
> http://homepage.mac.com/jakerobb/ow.pdf
(Continue reading)

Jake Robb | 2 Dec 2003 06:23
Picon

Re: funky rendering bug

Karl,

Thanks for checking out the bug.

I tried saving the screenshot PDF as a JPG, but it increased in size from
160K to 164, so I went with the PDF.  I apologize for the image size; I
didn't think that 160 was that bad (but then again, having just upgraded
from 1.5Mbps cable to 3.5, my standards have changed from when I used 28.8).

-Jake

Karl Kuehn wrote:

> This page does indeed do a good job of exposing some bugs in the
> rendering system on OmniWeb... I was not able to get the same bug, but
> did get this one:
> 
> http://larkost.dyndns.info/Picture3.png
> 
> The little movement triangle on the corner of the window followed the
> content up and down when I use my scroll wheel. It was quite amusing.
> 
> Karl Kuehn
> larkost <at> softhome.net
> 
> PS... Jake Robb... in the future please do not post screen-capture
> pdf's... If you are on MacOS 10.3, open the pdf in preview.app, and
> export to a better format, such as png. And at least use it to crop the
> image. 150 some k for an image is a bit excessive... especially for
> those of us on dial-up at home (no service here... *sigh*).
(Continue reading)

Jonathan Tyzack | 3 Dec 2003 10:41
Picon

Re: funky rendering bug

Hi,

this bug also occurs at MacUser UK as well (which is probably published 
by the same company looking at the similar styles of the page layout).

I see that you have a .Mac account, Jake. If so, I highly recommend 
downloading ImageWell for posting screenshots to your account. It's a 
menubar icon that allows you to drag and drop screenshots to it for 
quick and easy scaling and conversion to .jpgs prior to posting it to 
the folder of your choice on your iDisk:

http://homepage.mac.com/jtyzack/.Pictures/screenshots/imagewell1.jpg

http://homepage.mac.com/jtyzack/.Pictures/screenshots/imagewell2.jpg

http://homepage.mac.com/jtyzack/.Pictures/screenshots/imagewell3.jpg

Putting it simply, it rocks!

See macupdate for it:

http://www.macupdate.com/info.php/id/11375

Cheers,

Jonathan

P.S. It isn't limited to use with a .Mac account, it can also be used 
with other WebDAV accounts and for FTP too.

(Continue reading)

Ward Clark | 6 Dec 2003 17:33

OmniWeb weather forecast is bleak

The Weather.com site seems to be seriously OmniWeb-unfriendly:

1.  When I fill in my Zip code in the "local forecast" banner, select a  
#2 choice, and click "GO!", nothing happens.

	http://www.weather.com/

Hitting "return" instead of clicking "GO!" also does nothing.

2.  Using a old bookmark, I'm able to get my local forecast:

	http://www.weather.com/outlook/health/local/ 
USMA0424?promo=english&code=384068&site=magnet&par=internal

However, when I click on the "Map in Motion" link (below the default  
radar map), the following page loads but the weather map animation  
never appears.

	http://www.weather.com/outlook/homeandgarden/map/ 
USMA0424?from=LAPmaps&name=index_large_animated&day=1

Safari half works:  The local forecast (#1) works fine, but the map in  
motion never appears.

Explorer works fine in both cases.

-- Ward (registered OW user & New England weather-watcher)
Mark Bisaha | 6 Dec 2003 19:59
Picon

loading behavior

OW frequently seems to hang when loading the final element of a page. 
At a number of different sites it'll keep spinning its gear as it loads 
"71 of 72 items" or "23 of 24 items" or whatever the particular number 
may be. If I want to press a button on a page while this is occurring, 
I first have to press Stop (toolbar) or else the button won't take as 
everything grinds to a halt waiting for that final element to load, 
which often never happens.

Anyone else have this?

Kind regards,

Mark
Karl Kuehn | 6 Dec 2003 20:38
Picon

Re: OmniWeb weather forecast is bleak

	This is a mistake on the WebPage developer's part... a small but 
confusing one. The mistake is that the developer is trying to "return" 
a variable from an onSubmit callback... as if it were a subroutine. It 
OmniWeb seems to trip over the bad coding.
	For those who want to play along at home, search for the string 
"checkForm()" in the source code, remove the "return" before it, and 
then have OmniWeb redisplay the modified page. It will now work.

	On the animated map part... some developer has taken a very simple 
thing (changing an image with a timer callback), and made it into a 
monstrosity... There is so much JavaScript in that page... I got a 
headache wading trough ti to try and find out what is going wrong. My 
guess is that there is a bug in all the code that tries to deal with 
various browsers, one that is mis-filing OmniWeb... To me this is 
simple: all browsers have the document.images array, and then load the 
images into the browser by making 1x1 img tags at the bottom of the 
page with either and onLoad handler on the page, or on the individual 
images to tell you when you are ready to go...
	Someone got way to involved on trying to do it a single way... Oh... 
and their feedback page for JavaScript problems is a dead link... 
*sigh*

		Karl Kuehn
			larkost <at> softhome.net

On Dec 6, 2003, at 11:33 AM, Ward Clark wrote:

> The Weather.com site seems to be seriously OmniWeb-unfriendly:
>
> 1.  When I fill in my Zip code in the "local forecast" banner, select 
(Continue reading)

Jake Robb | 6 Dec 2003 21:22
Picon

Re: OmniWeb weather forecast is bleak

Karl,

Are you referring to this bit?

onSubmit="return checkForm();"

If so, that's valid JavaScript.  The form will use the function checkForm()
as a validator.  If checkForm() returns false, the form doesn't submit.

Typically, one gets this behavior if the JavaScript in the validator
function has an error.  I haven't looked for the error yet.

-Jake

Karl Kuehn wrote:

> This is a mistake on the WebPage developer's part... a small but
> confusing one. The mistake is that the developer is trying to "return"
> a variable from an onSubmit callback... as if it were a subroutine. It
> OmniWeb seems to trip over the bad coding.
> For those who want to play along at home, search for the string
> "checkForm()" in the source code, remove the "return" before it, and
> then have OmniWeb redisplay the modified page. It will now work.
> 
> On the animated map part... some developer has taken a very simple
> thing (changing an image with a timer callback), and made it into a
> monstrosity... There is so much JavaScript in that page... I got a
> headache wading trough ti to try and find out what is going wrong. My
> guess is that there is a bug in all the code that tries to deal with
> various browsers, one that is mis-filing OmniWeb... To me this is
(Continue reading)

Mathias Terreaux | 6 Dec 2003 21:23
Picon
Favicon

Re: loading behavior

Mark Bisaha <markbisaha <at> mac.com> wrote:

> OW frequently seems to hang when loading the final element of a page.
> At a number of different sites it'll keep spinning its gear as it loads
> "71 of 72 items" or "23 of 24 items" or whatever the particular number
> may be. If I want to press a button on a page while this is occurring,
> I first have to press Stop (toolbar) or else the button won't take as
> everything grinds to a halt waiting for that final element to load, 
> which often never happens.
> 
> Anyone else have this?

yes I have this problem sometimes.
And usually the page doesn't display totaly until I 'stop' loading

as I remember, in the activity monitor, I see that OW is doing something
with 'orphans'...

Gmane