Hello, we understand you guys may be able to help.

We have a page which has been working great for over a year and gets many
hits. However recently something got changed that we cannot seem to find,
and now *sometimes* if you refresh the page (generally while it is still
loading) in IE7, we get the popup window error:

Internet Explorer cannot open the Internet site...
Operation aborted

Here is an example of the page in question:
http://tinyurl.com/35mwxr [broadband recommended]

We appreciate you may have other comments on the site such as the size of
the pages, however we are not looking to change that at present, with faster
broadband becoming more abundant. Search engine listings alert the user
that broadband is recommended for this technology.

As we said, the site worked great, but for this unknown reason now needs
some sort of a tweak to fix. The changes we made before it happened were
related to the body tag but they have been completely undone yet the issue
remains :-S

Thanks in advance to anyone able to find the cure for us to test.

Regards,
Mika [at] SHS.com

Mika wrote:
> Internet Explorer cannot open the Internet site...
> Operation aborted

That happens on IE when you try to add items to the DOM before the page
is complete. Wait for onload event to fire before doing it, or poll the
document.readyState waiting for "complete" (although "interactive" may
sometimes be good enough).

Well bust mah britches and call me cheeky, on Fri, 16 Nov 2007 18:12:37
GMT Mika scribed:

> Hello, we understand you guys may be able to help.
>
> We have a page which has been working great for over a year and gets
> many hits. However recently something got changed that we cannot seem
> to find, and now *sometimes* if you refresh the page (generally while
> it is still loading) in IE7, we get the popup window error:
>
> Internet Explorer cannot open the Internet site...
> Operation aborted
>
> Here is an example of the page in question:
> http://tinyurl.com/35mwxr [broadband recommended]
>
> We appreciate you may have other comments on the site such as the size
> of the pages, however we are not looking to change that at present,
> with faster broadband becoming more abundant. Search engine listings
> alert the user that broadband is recommended for this technology.
>
> As we said, the site worked great, but for this unknown reason now
> needs some sort of a tweak to fix. The changes we made before it
> happened were related to the body tag but they have been completely
> undone yet the issue remains :-S
>
> Thanks in advance to anyone able to find the cure for us to test.

I did a refresh-while-loading in Opera and got tons of errors, probably
related to the javascript (...apparently being interrupted). Oth, a
refresh-post-load produced no errors in the same browser. Ergo, I suspect
that the abundant j/s is causing the problem. Suggest you try ie7 without
the j/s on.

--
Bone Ur
Cavemen have formidable pheromones.

"Bone Ur" <monstersquasher [at] yahoo.com> wrote in message
news:Xns99EA771344129boneurhyphe [at] 85.214.90.236...
> Well bust mah britches and call me cheeky, on Fri, 16 Nov 2007 18:12:37
> GMT Mika scribed:
>
>> Hello, we understand you guys may be able to help.
>>
>> We have a page which has been working great for over a year and gets
>> many hits. However recently something got changed that we cannot seem
>> to find, and now *sometimes* if you refresh the page (generally while
>> it is still loading) in IE7, we get the popup window error:
>>
>> Internet Explorer cannot open the Internet site...
>> Operation aborted
>>
>> Here is an example of the page in question:
>> http://tinyurl.com/35mwxr [broadband recommended]
>>
>> We appreciate you may have other comments on the site such as the size
>> of the pages, however we are not looking to change that at present,
>> with faster broadband becoming more abundant. Search engine listings
>> alert the user that broadband is recommended for this technology.
>>
>> As we said, the site worked great, but for this unknown reason now
>> needs some sort of a tweak to fix. The changes we made before it
>> happened were related to the body tag but they have been completely
>> undone yet the issue remains :-S
>>
>> Thanks in advance to anyone able to find the cure for us to test.
>
> I did a refresh-while-loading in Opera and got tons of errors, probably
> related to the javascript (...apparently being interrupted). Oth, a
> refresh-post-load produced no errors in the same browser. Ergo, I suspect
> that the abundant j/s is causing the problem. Suggest you try ie7 without
> the j/s on.

Thanks Bone, however as j/s in crucial we wonder if there is a workaround
you can think of to this?

"Stevo" <please [at] spam-me.com> wrote in message
news:fhko5q$31l$00$1 [at] news.t-online.com...
> Mika wrote:
>> Internet Explorer cannot open the Internet site...
>> Operation aborted
>
> That happens on IE when you try to add items to the DOM before the page is
> complete. Wait for onload event to fire before doing it, or poll the
> document.readyState waiting for "complete" (although "interactive" may
> sometimes be good enough).

Thanks Stevo.

Can you elaborate on how we could make the Document Object Model only happen
after onload, or better still implement your polling suggestion.

I am not one of the programmers myself, but would appreciate it if you could
briefly explain in layman's terms what should be done. I.e. "Find and
change <body onload=... to xxxx", so we can try it here. Many thanks.

"Bone Ur" <monstersquasher [at] yahoo.com> wrote in message
news:Xns99EA771344129boneurhyphe [at] 85.214.90.236...
> Well bust mah britches and call me cheeky, on Fri, 16 Nov 2007 18:12:37
> GMT Mika scribed:
>
>> Hello, we understand you guys may be able to help.
>>
>> We have a page which has been working great for over a year and gets
>> many hits. However recently something got changed that we cannot seem
>> to find, and now *sometimes* if you refresh the page (generally while
>> it is still loading) in IE7, we get the popup window error:
>>
>> Internet Explorer cannot open the Internet site...
>> Operation aborted
>>
>> Here is an example of the page in question:
>> http://tinyurl.com/35mwxr [broadband recommended]
>>
>> We appreciate you may have other comments on the site such as the size
>> of the pages, however we are not looking to change that at present,
>> with faster broadband becoming more abundant. Search engine listings
>> alert the user that broadband is recommended for this technology.
>>
>> As we said, the site worked great, but for this unknown reason now
>> needs some sort of a tweak to fix. The changes we made before it
>> happened were related to the body tag but they have been completely
>> undone yet the issue remains :-S
>>
>> Thanks in advance to anyone able to find the cure for us to test.
>
> I did a refresh-while-loading in Opera and got tons of errors, probably
> related to the javascript (...apparently being interrupted). Oth, a
> refresh-post-load produced no errors in the same browser. Ergo, I suspect
> that the abundant j/s is causing the problem. Suggest you try ie7 without
> the j/s on.

PS: Due to Opera functionality limitations (partly on the width of
streetscape pages) that browser is not supported by our site, although what
you found out is interesting.

Well bust mah britches and call me cheeky, on Fri, 16 Nov 2007 22:07:09
GMT Mika scribed:

>>> Thanks in advance to anyone able to find the cure for us to test.
>>
>> I did a refresh-while-loading in Opera and got tons of errors,
>> probably related to the javascript (...apparently being interrupted).
>> Oth, a refresh-post-load produced no errors in the same browser.
>> Ergo, I suspect that the abundant j/s is causing the problem.
>> Suggest you try ie7 without the j/s on.
>
> PS: Due to Opera functionality limitations (partly on the width of
> streetscape pages) that browser is not supported by our site, although
> what you found out is interesting.

I notice you're using an "shtml" extension, but...

Here's something to try. I emphasize it's just a test. Change your
extension to php and see what happens. (I hope your server supports it.)
The idea relates to caching; who knows, maybe it'll make a difference.

--
Bone Ur
Cavemen have formidable pheromones.

"Bone Ur" <monstersquasher [at] yahoo.com> wrote in message
news:Xns99EAA431A8663boneurhyphe [at] 85.214.90.236...
> Well bust mah britches and call me cheeky, on Fri, 16 Nov 2007 22:07:09
> GMT Mika scribed:
>
>>>> Thanks in advance to anyone able to find the cure for us to test.
>>>
>>> I did a refresh-while-loading in Opera and got tons of errors,
>>> probably related to the javascript (...apparently being interrupted).
>>> Oth, a refresh-post-load produced no errors in the same browser.
>>> Ergo, I suspect that the abundant j/s is causing the problem.
>>> Suggest you try ie7 without the j/s on.
>>
>> PS: Due to Opera functionality limitations (partly on the width of
>> streetscape pages) that browser is not supported by our site, although
>> what you found out is interesting.
>
> I notice you're using an "shtml" extension, but...
>
> Here's something to try. I emphasize it's just a test. Change your
> extension to php and see what happens. (I hope your server supports it.)
> The idea relates to caching; who knows, maybe it'll make a difference.

It seems to work! Can anyone replicate the old bug at the new php page?
http://tinyurl.com/324enb

"Bone Ur" <monstersquasher [at] yahoo.com> wrote in message
news:Xns99EAA431A8663boneurhyphe [at] 85.214.90.236...
> Well bust mah britches and call me cheeky, on Fri, 16 Nov 2007 22:07:09
> GMT Mika scribed:
>
>>>> Thanks in advance to anyone able to find the cure for us to test.
>>>
>>> I did a refresh-while-loading in Opera and got tons of errors,
>>> probably related to the javascript (...apparently being interrupted).
>>> Oth, a refresh-post-load produced no errors in the same browser.
>>> Ergo, I suspect that the abundant j/s is causing the problem.
>>> Suggest you try ie7 without the j/s on.
>>
>> PS: Due to Opera functionality limitations (partly on the width of
>> streetscape pages) that browser is not supported by our site, although
>> what you found out is interesting.
>
> I notice you're using an "shtml" extension, but...
>
> Here's something to try. I emphasize it's just a test. Change your
> extension to php and see what happens. (I hope your server supports it.)
> The idea relates to caching; who knows, maybe it'll make a difference.

That does work http://tinyurl.com/324enb so the theory is sound BUT the
problem is php does to work correctly with our Google Maps integration, and
also we use SSI such as <!--#include virtual="/_borders/top.htm"--> which is
why we need shtml.

Mika wrote:
idea relates to caching; who knows, maybe it'll make a difference.
>
> That does work http://tinyurl.com/324enb so the theory is sound BUT the
> problem is php does to work correctly with our Google Maps integration, and
> also we use SSI such as <!--#include virtual="/_borders/top.htm"--> which is
> why we need shtml.

Ah but you can easily convert that to php like this:

<?php include_once("/_borders/top.htm"); ?>


and forego the SSI


--
Take care,

Jonathan
-------------------
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com

Mika wrote:


>
> That does work http://tinyurl.com/324enb so the theory is sound BUT the
> problem is php does to work correctly with our Google Maps integration,
> and
> also we use SSI such as <!--#include virtual="/_borders/top.htm"-->
> which is
> why we need shtml.
>
>

If you use Apache, you can use rewrite_mod.
A URI doesn't need to hold the name of the resource on the server side.

Anyway, changing the URI terminal characters shouldn't change the behavior
of user agents.
The fact is: Opera and probably some others RFC-2616 conforming user
agents doesn't cache, by default, resources the URI of which contains a
request string following a question mark.
Please, don't rely on this ridiculous hack. Use proper HTTP headers to
prevent caching.

--
If you've a question that doesn't belong to Usenet, contact me at
<tabkanDELETETHISnaz [at] yahoDELETETHATo.fr>

"André Gillibert" <tabkanDELETETHISnaz [at] yahodeletethato.fr> wrote in message
news:op.t1xi9iri7pu1mk [at] andre...
> Mika wrote:
>
>
>>
>> That does work http://tinyurl.com/324enb so the theory is sound BUT the
>> problem is php does to work correctly with our Google Maps integration,
>> and
>> also we use SSI such as <!--#include virtual="/_borders/top.htm"-->
>> which is
>> why we need shtml.
>>
>>
>
> If you use Apache, you can use rewrite_mod.
> A URI doesn't need to hold the name of the resource on the server side.
>
> Anyway, changing the URI terminal characters shouldn't change the behavior
> of user agents.
> The fact is: Opera and probably some others RFC-2616 conforming user
> agents doesn't cache, by default, resources the URI of which contains a
> request string following a question mark.
> Please, don't rely on this ridiculous hack. Use proper HTTP headers to
> prevent caching.

I agree. What headers should we try?

Is it as simple as changing the doctype?

Thanks for all the help so far.

> --
> If you've a question that doesn't belong to Usenet, contact me at
> <tabkanDELETETHISnaz [at] yahoDELETETHATo.fr>

"Jonathan N. Little" <lws4art [at] centralva.net> wrote in message
news:c8599$473e469c$40cba7c2$7127 [at] NAXS.COM...
> Mika wrote:
> idea relates to caching; who knows, maybe it'll make a difference.
>>
>> That does work http://tinyurl.com/324enb so the theory is sound BUT the
>> problem is php does to work correctly with our Google Maps integration,
>> and also we use SSI such as <!--#include virtual="/_borders/top.htm"-->
>> which is why we need shtml.
>
> Ah but you can easily convert that to php like this:
>
> <?php include_once("/_borders/top.htm"); ?>
>
>
> and forego the SSI

That would be great, but our map code is still thrown completely off by
using php. If you try to walk along the street, the map walks the wrong
way, the man does not appear, etc. It looks like we need a solution that
works with shtml. Perhaps changing the doctype?

Mika wrote:
> "Jonathan N. Little" <lws4art [at] centralva.net> wrote in message
> news:c8599$473e469c$40cba7c2$7127 [at] NAXS.COM...
>> Mika wrote:
>> idea relates to caching; who knows, maybe it'll make a difference.
>>> That does work http://tinyurl.com/324enb so the theory is sound BUT the
>>> problem is php does to work correctly with our Google Maps integration,
>>> and also we use SSI such as <!--#include virtual="/_borders/top.htm"-->
>>> which is why we need shtml.
>> Ah but you can easily convert that to php like this:
>>
>> <?php include_once("/_borders/top.htm"); ?>
>>
>>
>> and forego the SSI
>
> That would be great, but our map code is still thrown completely off by
> using php. If you try to walk along the street, the map walks the wrong
> way, the man does not appear, etc. It looks like we need a solution that
> works with shtml. Perhaps changing the doctype?
>
>
Oh that site...I remember a what was it a couple of year ago...

Well if there was ever a concept not conducive to html, this is it! What
you really want is Flash, (Yes Travis, if he really want to do this
thing Flash would be far better) sand progressively load sections...

--
Take care,

Jonathan
-------------------
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com

Jonathan N. Little wrote:

> Oh that site...I remember a what was it a couple of year ago...
Not sure how my "s" wandered all the way from.............^

>
> Well if there was ever a concept not conducive to html, this is it! What
> you really want is Flash, (Yes Travis, if he really want to do this
> thing Flash would be far better) sand progressively load sections...
all the way down here!.............^

Damn gypsy "s"!


--
Take care,

Jonathan
-------------------
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com

"Jonathan N. Little" <lws4art [at] centralva.net> wrote in message
news:8ccc6$473ee9e6$40cba7aa$8293 [at] NAXS.COM...
> Mika wrote:
>> "Jonathan N. Little" <lws4art [at] centralva.net> wrote in message
>> news:c8599$473e469c$40cba7c2$7127 [at] NAXS.COM...
>>> Mika wrote:
>>> idea relates to caching; who knows, maybe it'll make a difference.
>>>> That does work http://tinyurl.com/324enb so the theory is sound BUT the
>>>> problem is php does to work correctly with our Google Maps integration,
>>>> and also we use SSI such as <!--#include virtual="/_borders/top.htm"-->
>>>> which is why we need shtml.
>>> Ah but you can easily convert that to php like this:
>>>
>>> <?php include_once("/_borders/top.htm"); ?>
>>>
>>>
>>> and forego the SSI
>>
>> That would be great, but our map code is still thrown completely off by
>> using php. If you try to walk along the street, the map walks the wrong
>> way, the man does not appear, etc. It looks like we need a solution that
>> works with shtml. Perhaps changing the doctype?
> Oh that site...I remember a what was it a couple of year ago...
>
> Well if there was ever a concept not conducive to html, this is it! What
> you really want is Flash, (Yes Travis, if he really want to do this thing
> Flash would be far better) sand progressively load sections...

Whilst we appreciate the feedback, the site works perfectly well - aside
from this new bug which has crept in. That is really all we are looking for
your advice with, and understood someone here might have a neat simple
solution. In some of the other discussions we are almost there.

I hope you appreciate that with some much work done and the site working, we
are not about to completely rewrite it in Flash because of one small glitch.
Simpler to fix the glitch.

Thanks in advance to anyone able to help with that.

Accidentally I have read this thread and I noticed that the KB article
I linked in "Active time for HTTP connection" thread may be giving
another possible hint:

http://support.microsoft.com/kb/813827

"If you set the KeepAliveTimeout value to less than 60,000 (one
minute), you may have problems communicating with Web servers that
require persistent HTTP connections. For example, you may receive a
"Page cannot be displayed" error message."

It may be possible that some visitors have KeepAliveTimeout manually
set to too short, or that for some requests the inactivity period goes
beyond the default allowed 60,000ms

I cannot reproduce your problem neither in IE6 nor IE7 so just
guessing. If you have a machine stable reproducing the problem, then I
would check one by one:
1) HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion
\InternetSettings
Try to set KeepAliveTimeout DWORD value to 180000 and add new key
ServerInfoTimeout with DWORD value to 180000

2) Tools :: Internet Options :: Advanced :: HTTP 1.1 settings :: check
on "Use HTTP 1.1 through proxy connections"
(default is off)

VK wrote:
> Accidentally I have read this thread and I noticed that the KB article
> I linked in "Active time for HTTP connection" thread may be giving
> another possible hint:
>
> http://support.microsoft.com/kb/813827
>
> "If you set the KeepAliveTimeout value to less than 60,000 (one
> minute), you may have problems communicating with Web servers that
> require persistent HTTP connections. For example, you may receive a
> "Page cannot be displayed" error message."
>
> It may be possible that some visitors have KeepAliveTimeout manually
> set to too short, or that for some requests the inactivity period goes
> beyond the default allowed 60,000ms
>
> I cannot reproduce your problem neither in IE6 nor IE7 so just
> guessing. If you have a machine stable reproducing the problem, then I
> would check one by one:
> 1) HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion
> \InternetSettings
> Try to set KeepAliveTimeout DWORD value to 180000 and add new key
> ServerInfoTimeout with DWORD value to 180000
>
> 2) Tools :: Internet Options :: Advanced :: HTTP 1.1 settings :: check
> on "Use HTTP 1.1 through proxy connections"
> (default is off)

If this is the case because the OP's "web app" requires such delays in
order process and transmit the site do you really expect visitors to
hack their default Windows' registry just to see the site? And we have
long-winded arguments whether or not the average user understands the
browser back button!

--
Take care,

Jonathan
-------------------
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com

On Nov 17, 8:13 pm, "Jonathan N. Little" <lws4... [at] centralva.net>
wrote:
> If this is the case because the OP's "web app" requires such delays in
> order process and transmit the site do you really expect visitors to
> hack their default Windows' registry just to see the site?

Of course not! We are on the stage of identifying the problem, not
solving it. If my guess is correct - but it may be very well wrong -
then OP has to think of a server-side adjustment to ensure that the
inactivity period will never exceed the default KeepAliveTimeout.
There is a number of such workarounds.

P.S. Also if this is a problem then the question also gets OT for this
NG and should be transferred to some server scripting group, depending
on used server-side software.

"VK" <schools_ring [at] yahoo.com> wrote in message
news:3b3cdd69-19c1-4954-998f-b618f1354629 [at] n20g2000hsh.google groups.com...
> Accidentally I have read this thread and I noticed that the KB article
> I linked in "Active time for HTTP connection" thread may be giving
> another possible hint:
>
> http://support.microsoft.com/kb/813827
>
> "If you set the KeepAliveTimeout value to less than 60,000 (one
> minute), you may have problems communicating with Web servers that
> require persistent HTTP connections. For example, you may receive a
> "Page cannot be displayed" error message."

Thank you however that is not the error message we receive. 'Operation
aborted' is the error, and only when refreshing the page whilst it is still
loading. I do not feel this error is likely to relate, but thank you
anyway...

> It may be possible that some visitors have KeepAliveTimeout manually
> set to too short, or that for some requests the inactivity period goes
> beyond the default allowed 60,000ms
>
> I cannot reproduce your problem neither in IE6 nor IE7 so just
> guessing. If you have a machine stable reproducing the problem, then I
> would check one by one:

Have you tried refreshing the page multiple times whilst it is still
loading? The error does not occur every time.

> 1) HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion
> \InternetSettings
> Try to set KeepAliveTimeout DWORD value to 180000 and add new key
> ServerInfoTimeout with DWORD value to 180000
>
> 2) Tools :: Internet Options :: Advanced :: HTTP 1.1 settings :: check
> on "Use HTTP 1.1 through proxy connections"
> (default is off)

> Thank you however that is not the error message we receive. 'Operation
> aborted' is the error, and only when refreshing the page whilst it is still
> loading.

Then the KISS rules as usual I guess... :-)

http://www.ryangrant.net/archives/internet-explorer-cannot-o pen-the-internet-site-operation-aborted-google-map-api

On Nov 17, 11:06 pm, VK <schools_r... [at] yahoo.com> wrote:
> Then the KISS rules as usual I guess... :-)

"KISS rulez" of course :-)

P.S. KISS: a Silicon Valley programming community acronym staying from
"Keep It Simple, Stupid"
A humorous variation of Occam's razor.
In my last post targeted to myself, not to OP.

"VK" <schools_ring [at] yahoo.com> wrote in message
news:08f752a4-3793-4bd1-9c61-86c4a2f38bc9 [at] a28g2000hsc.google groups.com...
>> Thank you however that is not the error message we receive. 'Operation
>> aborted' is the error, and only when refreshing the page whilst it is
>> still
>> loading.
>
> Then the KISS rules as usual I guess... :-)
>
> http://www.ryangrant.net/archives/internet-explorer-cannot-o pen-the-internet-site-operation-aborted-google-map-api

Well thank you for that link. We have spent 2 hours trying every solution
that would work for our page.

The basic idea is to move the Google Maps j/s (the culprit along with IE)
*outside* the body tags. Give it an out of body experience.

This did indeed fix the bug however it also introduced a problem with the
start percentage j/s we had to show FF where to begin showing the street
(e.g. it shows Oxford Street starting in the middle).

So frustrating as that is the solution, but Google Maps j/s doesn't like
being outside the body tag for some advanced options.

I wonder if anyone has any other ideas along these lines?

On Fri, 16 Nov 2007 18:12:37 GMT, in comp.lang.javascript "Mika"
<anon [at] anon.com>
<p4l%i.48642$c_1.38326 [at] text.news.blueyonder.co.uk> wrote:

>| Hello, we understand you guys may be able to help.
>|
>| We have a page which has been working great for over a year and gets many
>| hits. However recently something got changed that we cannot seem to find,
>| and now *sometimes* if you refresh the page (generally while it is still
>| loading) in IE7, we get the popup window error:
>|
>| Internet Explorer cannot open the Internet site...
>| Operation aborted
>|
>| Here is an example of the page in question:
>| http://tinyurl.com/35mwxr [broadband recommended]
>|
>| We appreciate you may have other comments on the site such as the size of
>| the pages, however we are not looking to change that at present, with faster
>| broadband becoming more abundant. Search engine listings alert the user
>| that broadband is recommended for this technology.
>|
>| As we said, the site worked great, but for this unknown reason now needs
>| some sort of a tweak to fix. The changes we made before it happened were
>| related to the body tag but they have been completely undone yet the issue
>| remains :-S
>|
>| Thanks in advance to anyone able to find the cure for us to test.

I'd fix up the errors/warnings within the html first.
-----------------------------------------------------
Result: 0 errors / 139 warnings

line 8 column 1 - Warning: <meta> element not empty or not closed
line 10 column 1 - Warning: <meta> element not empty or not closed
line 11 column 1 - Warning: <link> element not empty or not closed
line 14 column 1 - Warning: <link> element not empty or not closed
line 20 column 1 - Warning: <meta> element not empty or not closed
line 27 column 1 - Warning: <meta> element not empty or not closed
line 30 column 1 - Warning: discarding unexpected <head>
line 31 column 1 - Warning: <meta> element not empty or not closed
line 49 column 6 - Warning: <img> element not empty or not closed
line 51 column 6 - Warning: <img> element not empty or not closed
line 63 column 11 - Warning: <img> element not empty or not closed
line 68 column 9 - Warning: <img> element not empty or not closed
line 72 column 9 - Warning: <img> element not empty or not closed
line 88 column 11 - Warning: <img> element not empty or not closed
line 93 column 9 - Warning: <img> element not empty or not closed
line 97 column 9 - Warning: <img> element not empty or not closed
line 113 column 11 - Warning: <img> element not empty or not closed
line 118 column 9 - Warning: <img> element not empty or not closed
line 122 column 9 - Warning: <img> element not empty or not closed
line 131 column 6 - Warning: <img> element not empty or not closed
line 221 column 6 - Warning: <img> element not empty or not closed
line 227 column 78 - Warning: <font> unexpected or duplicate quote
mark
line 227 column 78 - Warning: <font> unexpected or duplicate quote
mark
line 227 column 78 - Warning: <font> dropping value "#FFFFFF" for
repeated attribute "color"
line 227 column 6 - Warning: <img> element not empty or not closed
line 238 column 77 - Warning: <font> unexpected or duplicate quote
mark
line 238 column 77 - Warning: <font> unexpected or duplicate quote
mark
line 238 column 77 - Warning: <font> dropping value "#FFFFFF" for
repeated attribute "color"
line 238 column 6 - Warning: <img> element not empty or not closed
line 243 column 6 - Warning: <img> element not empty or not closed
line 247 column 82 - Warning: <font> unexpected or duplicate quote
mark
line 247 column 82 - Warning: <font> unexpected or duplicate quote
mark
line 247 column 6 - Warning: <img> element not empty or not closed
line 254 column 67 - Warning: <font> unexpected or duplicate quote
mark
line 254 column 67 - Warning: <font> unexpected or duplicate quote
mark
line 254 column 67 - Warning: <font> dropping value "#FFFFFF" for
repeated attribute "color"
line 266 column 3 - Warning: <img> element not empty or not closed
line 267 column 3 - Warning: <img> element not empty or not closed
line 268 column 3 - Warning: <img> element not empty or not closed
line 269 column 3 - Warning: <img> element not empty or not closed
line 36 column 1 - Warning: content occurs after end of body
line 36 column 1 - Warning: content occurs after end of body
line 303 column 1 - Warning: </head> isn't allowed in <body> elements
line 36 column 1 - Info: <body> previously mentioned
line 305 column 1 - Warning: discarding unexpected <body>
line 36 column 1 - Warning: content occurs after end of body
line 309 column 4 - Warning: <br> element not empty or not closed
line 311 column 14 - Warning: <br> element not empty or not closed
line 36 column 1 - Warning: content occurs after end of body
line 355 column 4 - Warning: <img> element not empty or not closed
line 359 column 4 - Warning: <img> element not empty or not closed
line 380 column 5 - Warning: missing </span> before <p>
line 382 column 77 - Warning: inserting implicit <span>
line 383 column 5 - Warning: discarding unexpected </span>
line 385 column 5 - Warning: <img> element not empty or not closed
line 406 column 6 - Warning: <embed> is not approved by W3C
line 406 column 6 - Warning: <embed> element not empty or not closed
line 412 column 5 - Warning: <img> element not empty or not closed
line 417 column 5 - Warning: <td> dropping value "326" for repeated
attribute "height"
line 426 column 7 - Warning: <img> element not empty or not closed
line 430 column 7 - Warning: <img> element not empty or not closed
line 435 column 7 - Warning: <img> element not empty or not closed
line 439 column 7 - Warning: <img> element not empty or not closed
line 447 column 7 - Warning: <img> element not empty or not closed
line 451 column 7 - Warning: <img> element not empty or not closed
line 457 column 7 - Warning: <img> element not empty or not closed
line 461 column 7 - Warning: <img> element not empty or not closed
line 470 column 7 - Warning: <img> element not empty or not closed
line 474 column 7 - Warning: <img> element not empty or not closed
line 481 column 7 - Warning: <img> element not empty or not closed
line 485 column 7 - Warning: <img> element not empty or not closed
line 36 column 1 - Warning: content occurs after end of body
line 501 column 3 - Warning: <img> element not empty or not closed
line 36 column 1 - Warning: content occurs after end of body
line 36 column 1 - Warning: content occurs after end of body
line 578 column 78 - Warning: '<' + '/' + letter not allowed here
line 583 column 53 - Warning: '<' + '/' + letter not allowed here
line 588 column 53 - Warning: '<' + '/' + letter not allowed here
line 36 column 1 - Warning: content occurs after end of body
line 36 column 1 - Warning: content occurs after end of body
line 595 column 1 - Warning: <head> isn't allowed in <body> elements
line 36 column 1 - Info: <body> previously mentioned
line 36 column 1 - Warning: content occurs after end of body
line 596 column 1 - Warning: <meta> isn't allowed in <body> elements
line 36 column 1 - Info: <body> previously mentioned
line 36 column 1 - Warning: content occurs after end of body
line 597 column 1 - Warning: <link> isn't allowed in <body> elements
line 36 column 1 - Info: <body> previously mentioned
line 597 column 1 - Warning: <link> element not empty or not closed
line 36 column 1 - Warning: content occurs after end of body
line 598 column 1 - Warning: </head> isn't allowed in <body> elements
line 36 column 1 - Info: <body> previously mentioned
line 600 column 1 - Warning: discarding unexpected <body>
line 36 column 1 - Warning: content occurs after end of body
line 602 column 59 - Warning: <br> element not empty or not closed
line 36 column 1 - Warning: content occurs after end of body
line 606 column 3 - Warning: <img> element not empty or not closed
line 607 column 3 - Warning: <img> element not empty or not closed
line 608 column 3 - Warning: <img> element not empty or not closed
line 609 column 3 - Warning: <img> element not empty or not closed
line 36 column 1 - Warning: content occurs after end of body
line 637 column 4 - Warning: <img> element not empty or not closed
line 643 column 4 - Warning: <img> element not empty or not closed
line 647 column 4 - Warning: <img> element not empty or not closed
line 36 column 1 - Warning: content occurs after end of body
line 46 column 4 - Warning: <table> proprietary attribute "height"
line 54 column 7 - Warning: <table> proprietary attribute "height"
line 58 column 9 - Warning: <table> proprietary attribute "height"
line 79 column 7 - Warning: <table> proprietary attribute "height"
line 83 column 9 - Warning: <table> proprietary attribute "height"
line 104 column 7 - Warning: <table> proprietary attribute "height"
line 108 column 9 - Warning: <table> proprietary attribute "height"
line 136 column 6 - Warning: <script> inserting "type" attribute
line 227 column 6 - Warning: <img> proprietary attribute value
"absmiddle"
line 227 column 78 - Warning: <font> attribute "color" has invalid
value "#FFFFFF""
line 238 column 6 - Warning: <img> proprietary attribute value
"absmiddle"
line 238 column 77 - Warning: <font> attribute "color" has invalid
value "#FFFFFF""
line 243 column 6 - Warning: <img> proprietary attribute value
"absmiddle"
line 243 column 6 - Warning: <img> attribute "height" has invalid
value "14/"
line 247 column 6 - Warning: <img> proprietary attribute value
"absmiddle"
line 247 column 6 - Warning: <img> attribute "height" has invalid
value "16/"
line 247 column 82 - Warning: <font> attribute "color" has invalid
value "#FFFFFF""
line 254 column 67 - Warning: <font> attribute "color" has invalid
value "#FFFFFF""
line 308 column 19 - Warning: <font> attribute "size" has invalid
value "20px"
line 314 column 2 - Warning: <table> proprietary attribute "height"
line 317 column 4 - Warning: <table> proprietary attribute "height"
line 320 column 6 - Warning: <table> proprietary attribute
"bordercolor"
line 322 column 8 - Warning: <td> proprietary attribute "background"
line 370 column 3 - Warning: <table> proprietary attribute "height"
line 415 column 3 - Warning: <table> proprietary attribute
"background"
line 415 column 3 - Warning: <table> proprietary attribute "height"
line 417 column 5 - Warning: <td> attribute "height" lacks value
line 417 column 5 - Warning: <td> proprietary attribute "padding"
line 423 column 5 - Warning: <table> proprietary attribute "height"
line 432 column 7 - Warning: <iframe> proprietary attribute "border"
line 444 column 5 - Warning: <table> proprietary attribute "height"
line 467 column 5 - Warning: <table> proprietary attribute "height"
line 477 column 7 - Warning: <iframe> proprietary attribute "border"
line 477 column 7 - Warning: <iframe> proprietary attribute "target"
line 605 column 2 - Warning: <div> anchor "layer1" already defined
line 631 column 2 - Warning: <table> proprietary attribute "height"
line 643 column 4 - Warning: <img> proprietary attribute value
"texttop"
line 41 column 85 - Warning: trimming empty <font>
line 247 column 176 - Warning: trimming empty <span>
Info: Doctype given is "-//W3C//DTD XHTML 1.0 Transitional//EN"
Info: Document content looks like HTML Proprietary
-- ------------------------------------------------------------ -
jnorthau [at] yourpantsyahoo.com.au : Remove your pants to reply
-- ------------------------------------------------------------ -

On Nov 16, 12:12 pm, "Mika" <a... [at] anon.com> wrote:
> Hello, we understand you guys may be able to help.
>
> We have a page which has been working great for over a year and gets many
> hits. However recently something got changed that we cannot seem to find,
> and now *sometimes* if you refresh the page (generally while it is still
> loading) in IE7, we get the popup window error:
>
> Internet Explorer cannot open the Internet site...
> Operation aborted
>
> Here is an example of the page in question:http://tinyurl.com/35mwxr[broadband recommended]
>
> We appreciate you may have other comments on the site such as the size of
> the pages, however we are not looking to change that at present, with faster
> broadband becoming more abundant. Search engine listings alert the user
> that broadband is recommended for this technology.
>
> As we said, the site worked great, but for this unknown reason now needs
> some sort of a tweak to fix. The changes we made before it happened were
> related to the body tag but they have been completely undone yet the issue
> remains :-S
>
> Thanks in advance to anyone able to find the cure for us to test.
>
> Regards,
> Mika [at] SHS.com

I don't know how accurate this is... but I read once that tables kind
of 'render twice' in most browsers (now don't flame me, I can't
remember why or where or if this was true...) but I had the same sort
of issue! Turns out, I had a large table containing my google map. I
was trying to modify my google map after it displayed on the screen,
but not necessarily after page load. I then put it into the onload
function - my call to modify my map. This then made my error HARDLY
reproducable. After searching around, I had the hunch that I should
remove the table from the layout of that code (I inherited the site in
table format - and boss man wanted the map in there pronto - no
'fixing' stupid things... like layout with table). I redesigned that
one page to not use any tables, and my error went away.

Food for thought, my friend. Good luck.

"Mika" <anon [at] anon.com> wrote in message
news:p4l%i.48642$c_1.38326 [at] text.news.blueyonder.co.uk...
> Hello, we understand you guys may be able to help.
>
> We have a page which has been working great for over a year and gets many
> hits. However recently something got changed that we cannot seem to find,
> and now *sometimes* if you refresh the page (generally while it is still
> loading) in IE7, we get the popup window error:
>
> Internet Explorer cannot open the Internet site...
> Operation aborted
>
> Here is an example of the page in question:
> http://tinyurl.com/35mwxr [broadband recommended]
>
> We appreciate you may have other comments on the site such as the size of
> the pages, however we are not looking to change that at present, with
> faster broadband becoming more abundant. Search engine listings alert the
> user that broadband is recommended for this technology.
>
> As we said, the site worked great, but for this unknown reason now needs
> some sort of a tweak to fix. The changes we made before it happened were
> related to the body tag but they have been completely undone yet the issue
> remains :-S
>
> Thanks in advance to anyone able to find the cure for us to test.
>
> Regards,
> Mika [at] SHS.com

Well we just reverted to a backup of the site, and noted we had removed the
following apparently redundant CSS:

"Mika" <anon [at] anon.com> wrote in message
news:p4l%i.48642$c_1.38326 [at] text.news.blueyonder.co.uk...
> Hello, we understand you guys may be able to help.
>
> We have a page which has been working great for over a year and gets many
> hits. However recently something got changed that we cannot seem to find,
> and now *sometimes* if you refresh the page (generally while it is still
> loading) in IE7, we get the popup window error:
>
> Internet Explorer cannot open the Internet site...
> Operation aborted
>
> Here is an example of the page in question:
> http://tinyurl.com/35mwxr [broadband recommended]
>
> We appreciate you may have other comments on the site such as the size of
> the pages, however we are not looking to change that at present, with
> faster broadband becoming more abundant. Search engine listings alert the
> user that broadband is recommended for this technology.
>
> As we said, the site worked great, but for this unknown reason now needs
> some sort of a tweak to fix. The changes we made before it happened were
> related to the body tag but they have been completely undone yet the issue
> remains :-S
>
> Thanks in advance to anyone able to find the cure for us to test.
>
> Regards,
> Mika [at] SHS.com

Well we just restored a backup of the site and noted that we had removed the
following apparently redundant CSS:

<style type="text/css">
..style1 {
text-align: left;
}
..style32 {
text-align: center;
}
..style38 {
text-align: center;
}
..style39 {
color: #000000;
}
</style>

Reinstating this seems to have fixed the IE bug! Can anyone get the
'Operation aborted' window to appear now by refreshing this page WHILST it
is still working?
http://tinyurl.com/35mwxr

There was a mention to some style code in one of the fixes for this known IE
bug. Anyway, it now appears to be resolved.

Thanks for all the tips. Hopefully MS will fix the bug before even more
programmers hate their browser, even if the majority of public don't.

"Jeff North" <jnorthau [at] yahoo.com.au> wrote in message
news:j9ouj3hacf25adjjva1frldqklhv76fjo8 [at] 4ax.com...
> On Fri, 16 Nov 2007 18:12:37 GMT, in comp.lang.javascript "Mika"
> <anon [at] anon.com>
> <p4l%i.48642$c_1.38326 [at] text.news.blueyonder.co.uk> wrote:
>
>>| Hello, we understand you guys may be able to help.
>>|
>>| We have a page which has been working great for over a year and gets
>>many
>>| hits. However recently something got changed that we cannot seem to
>>find,
>>| and now *sometimes* if you refresh the page (generally while it is still
>>| loading) in IE7, we get the popup window error:
>>|
>>| Internet Explorer cannot open the Internet site...
>>| Operation aborted
>>|
>>| Here is an example of the page in question:
>>| http://tinyurl.com/35mwxr [broadband recommended]
>>|
>>| We appreciate you may have other comments on the site such as the size
>>of
>>| the pages, however we are not looking to change that at present, with
>>faster
>>| broadband becoming more abundant. Search engine listings alert the user
>>| that broadband is recommended for this technology.
>>|
>>| As we said, the site worked great, but for this unknown reason now needs
>>| some sort of a tweak to fix. The changes we made before it happened
>>were
>>| related to the body tag but they have been completely undone yet the
>>issue
>>| remains :-S
>>|
>>| Thanks in advance to anyone able to find the cure for us to test.
>
> I'd fix up the errors/warnings within the html first.
> -----------------------------------------------------
> Result: 0 errors / 139 warnings
>
> line 8 column 1 - Warning: <meta> element not empty or not closed
> line 10 column 1 - Warning: <meta> element not empty or not closed
> line 11 column 1 - Warning: <link> element not empty or not closed
> line 14 column 1 - Warning: <link> element not empty or not closed
> line 20 column 1 - Warning: <meta> element not empty or not closed
> line 27 column 1 - Warning: <meta> element not empty or not closed
> line 30 column 1 - Warning: discarding unexpected <head>
> line 31 column 1 - Warning: <meta> element not empty or not closed
> line 49 column 6 - Warning: <img> element not empty or not closed
> line 51 column 6 - Warning: <img> element not empty or not closed
> line 63 column 11 - Warning: <img> element not empty or not closed
> line 68 column 9 - Warning: <img> element not empty or not closed
> line 72 column 9 - Warning: <img> element not empty or not closed
> line 88 column 11 - Warning: <img> element not empty or not closed
> line 93 column 9 - Warning: <img> element not empty or not closed
> line 97 column 9 - Warning: <img> element not empty or not closed
> line 113 column 11 - Warning: <img> element not empty or not closed
> line 118 column 9 - Warning: <img> element not empty or not closed
> line 122 column 9 - Warning: <img> element not empty or not closed
> line 131 column 6 - Warning: <img> element not empty or not closed
> line 221 column 6 - Warning: <img> element not empty or not closed
> line 227 column 78 - Warning: <font> unexpected or duplicate quote
> mark
> line 227 column 78 - Warning: <font> unexpected or duplicate quote
> mark
> line 227 column 78 - Warning: <font> dropping value "#FFFFFF" for
> repeated attribute "color"
> line 227 column 6 - Warning: <img> element not empty or not closed
> line 238 column 77 - Warning: <font> unexpected or duplicate quote
> mark
> line 238 column 77 - Warning: <font> unexpected or duplicate quote
> mark
> line 238 column 77 - Warning: <font> dropping value "#FFFFFF" for
> repeated attribute "color"
> line 238 column 6 - Warning: <img> element not empty or not closed
> line 243 column 6 - Warning: <img> element not empty or not closed
> line 247 column 82 - Warning: <font> unexpected or duplicate quote
> mark
> line 247 column 82 - Warning: <font> unexpected or duplicate quote
> mark
> line 247 column 6 - Warning: <img> element not empty or not closed
> line 254 column 67 - Warning: <font> unexpected or duplicate quote
> mark
> line 254 column 67 - Warning: <font> unexpected or duplicate quote
> mark
> line 254 column 67 - Warning: <font> dropping value "#FFFFFF" for
> repeated attribute "color"
> line 266 column 3 - Warning: <img> element not empty or not closed
> line 267 column 3 - Warning: <img> element not empty or not closed
> line 268 column 3 - Warning: <img> element not empty or not closed
> line 269 column 3 - Warning: <img> element not empty or not closed
> line 36 column 1 - Warning: content occurs after end of body
> line 36 column 1 - Warning: content occurs after end of body
> line 303 column 1 - Warning: </head> isn't allowed in <body> elements
> line 36 column 1 - Info: <body> previously mentioned
> line 305 column 1 - Warning: discarding unexpected <body>
> line 36 column 1 - Warning: content occurs after end of body
> line 309 column 4 - Warning: <br> element not empty or not closed
> line 311 column 14 - Warning: <br> element not empty or not closed
> line 36 column 1 - Warning: content occurs after end of body
> line 355 column 4 - Warning: <img> element not empty or not closed
> line 359 column 4 - Warning: <img> element not empty or not closed
> line 380 column 5 - Warning: missing </span> before <p>
> line 382 column 77 - Warning: inserting implicit <span>
> line 383 column 5 - Warning: discarding unexpected </span>
> line 385 column 5 - Warning: <img> element not empty or not closed
> line 406 column 6 - Warning: <embed> is not approved by W3C
> line 406 column 6 - Warning: <embed> element not empty or not closed
> line 412 column 5 - Warning: <img> element not empty or not closed
> line 417 column 5 - Warning: <td> dropping value "326" for repeated
> attribute "height"
> line 426 column 7 - Warning: <img> element not empty or not closed
> line 430 column 7 - Warning: <img> element not empty or not closed
> line 435 column 7 - Warning: <img> element not empty or not closed
> line 439 column 7 - Warning: <img> element not empty or not closed
> line 447 column 7 - Warning: <img> element not empty or not closed
> line 451 column 7 - Warning: <img> element not empty or not closed
> line 457 column 7 - Warning: <img> element not empty or not closed
> line 461 column 7 - Warning: <img> element not empty or not closed
> line 470 column 7 - Warning: <img> element not empty or not closed
> line 474 column 7 - Warning: <img> element not empty or not closed
> line 481 column 7 - Warning: <img> element not empty or not closed
> line 485 column 7 - Warning: <img> element not empty or not closed
> line 36 column 1 - Warning: content occurs after end of body
> line 501 column 3 - Warning: <img> element not empty or not closed
> line 36 column 1 - Warning: content occurs after end of body
> line 36 column 1 - Warning: content occurs after end of body
> line 578 column 78 - Warning: '<' + '/' + letter not allowed here
> line 583 column 53 - Warning: '<' + '/' + letter not allowed here
> line 588 column 53 - Warning: '<' + '/' + letter not allowed here
> line 36 column 1 - Warning: content occurs after end of body
> line 36 column 1 - Warning: content occurs after end of body
> line 595 column 1 - Warning: <head> isn't allowed in <body> elements
> line 36 column 1 - Info: <body> previously mentioned
> line 36 column 1 - Warning: content occurs after end of body
> line 596 column 1 - Warning: <meta> isn't allowed in <body> elements
> line 36 column 1 - Info: <body> previously mentioned
> line 36 column 1 - Warning: content occurs after end of body
> line 597 column 1 - Warning: <link> isn't allowed in <body> elements
> line 36 column 1 - Info: <body> previously mentioned
> line 597 column 1 - Warning: <link> element not empty or not closed
> line 36 column 1 - Warning: content occurs after end of body
> line 598 column 1 - Warning: </head> isn't allowed in <body> elements
> line 36 column 1 - Info: <body> previously mentioned
> line 600 column 1 - Warning: discarding unexpected <body>
> line 36 column 1 - Warning: content occurs after end of body
> line 602 column 59 - Warning: <br> element not empty or not closed
> line 36 column 1 - Warning: content occurs after end of body
> line 606 column 3 - Warning: <img> element not empty or not closed
> line 607 column 3 - Warning: <img> element not empty or not closed
> line 608 column 3 - Warning: <img> element not empty or not closed
> line 609 column 3 - Warning: <img> element not empty or not closed
> line 36 column 1 - Warning: content occurs after end of body
> line 637 column 4 - Warning: <img> element not empty or not closed
> line 643 column 4 - Warning: <img> element not empty or not closed
> line 647 column 4 - Warning: <img> element not empty or not closed
> line 36 column 1 - Warning: content occurs after end of body
> line 46 column 4 - Warning: <table> proprietary attribute "height"
> line 54 column 7 - Warning: <table> proprietary attribute "height"
> line 58 column 9 - Warning: <table> proprietary attribute "height"
> line 79 column 7 - Warning: <table> proprietary attribute "height"
> line 83 column 9 - Warning: <table> proprietary attribute "height"
> line 104 column 7 - Warning: <table> proprietary attribute "height"
> line 108 column 9 - Warning: <table> proprietary attribute "height"
> line 136 column 6 - Warning: <script> inserting "type" attribute
> line 227 column 6 - Warning: <img> proprietary attribute value
> "absmiddle"
> line 227 column 78 - Warning: <font> attribute "color" has invalid
> value "#FFFFFF""
> line 238 column 6 - Warning: <img> proprietary attribute value
> "absmiddle"
> line 238 column 77 - Warning: <font> attribute "color" has invalid
> value "#FFFFFF""
> line 243 column 6 - Warning: <img> proprietary attribute value
> "absmiddle"
> line 243 column 6 - Warning: <img> attribute "height" has invalid
> value "14/"
> line 247 column 6 - Warning: <img> proprietary attribute value
> "absmiddle"
> line 247 column 6 - Warning: <img> attribute "height" has invalid
> value "16/"
> line 247 column 82 - Warning: <font> attribute "color" has invalid
> value "#FFFFFF""
> line 254 column 67 - Warning: <font> attribute "color" has invalid
> value "#FFFFFF""
> line 308 column 19 - Warning: <font> attribute "size" has invalid
> value "20px"
> line 314 column 2 - Warning: <table> proprietary attribute "height"
> line 317 column 4 - Warning: <table> proprietary attribute "height"
> line 320 column 6 - Warning: <table> proprietary attribute
> "bordercolor"
> line 322 column 8 - Warning: <td> proprietary attribute "background"
> line 370 column 3 - Warning: <table> proprietary attribute "height"
> line 415 column 3 - Warning: <table> proprietary attribute
> "background"
> line 415 column 3 - Warning: <table> proprietary attribute "height"
> line 417 column 5 - Warning: <td> attribute "height" lacks value
> line 417 column 5 - Warning: <td> proprietary attribute "padding"
> line 423 column 5 - Warning: <table> proprietary attribute "height"
> line 432 column 7 - Warning: <iframe> proprietary attribute "border"
> line 444 column 5 - Warning: <table> proprietary attribute "height"
> line 467 column 5 - Warning: <table> proprietary attribute "height"
> line 477 column 7 - Warning: <iframe> proprietary attribute "border"
> line 477 column 7 - Warning: <iframe> proprietary attribute "target"
> line 605 column 2 - Warning: <div> anchor "layer1" already defined
> line 631 column 2 - Warning: <table> proprietary attribute "height"
> line 643 column 4 - Warning: <img> proprietary attribute value
> "texttop"
> line 41 column 85 - Warning: trimming empty <font>
> line 247 column 176 - Warning: trimming empty <span>
> Info: Doctype given is "-//W3C//DTD XHTML 1.0 Transitional//EN"
> Info: Document content looks like HTML Proprietary

Thanks. There are no "errors" that we know of or can see, although there
are some warnings which do not affect the end result so can be ignored.

However can you suggest what the correct Doctype string should be if not the
current one?:

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=windows-1252">

....

Thanks!

"Jonathan N. Little" <lws4art [at] centralva.net> wrote in message
news:8ccc6$473ee9e6$40cba7aa$8293 [at] NAXS.COM...
> Mika wrote:
>> "Jonathan N. Little" <lws4art [at] centralva.net> wrote in message
>> news:c8599$473e469c$40cba7c2$7127 [at] NAXS.COM...
>>> Mika wrote:
>>> idea relates to caching; who knows, maybe it'll make a difference.
>>>> That does work http://tinyurl.com/324enb so the theory is sound BUT the
>>>> problem is php does to work correctly with our Google Maps integration,
>>>> and also we use SSI such as <!--#include virtual="/_borders/top.htm"-->
>>>> which is why we need shtml.
>>> Ah but you can easily convert that to php like this:
>>>
>>> <?php include_once("/_borders/top.htm"); ?>
>>>
>>>
>>> and forego the SSI
>>
>> That would be great, but our map code is still thrown completely off by
>> using php. If you try to walk along the street, the map walks the wrong
>> way, the man does not appear, etc. It looks like we need a solution that
>> works with shtml. Perhaps changing the doctype?
> Oh that site...I remember a what was it a couple of year ago...
>
> Well if there was ever a concept not conducive to html, this is it! What
> you really want is Flash, (Yes Travis, if he really want to do this thing
> Flash would be far better) sand progressively load sections...

Just as a point of interest, we chose HTML and j/s as the ability to add
affiliates' HTML and j/s 'eposters' to shop windows, draw imagemaps around
shop doors, and regularly update links etc. was much more straightforward if
using the same language the actual links use.

Also, loading the whole street first using Flash would have been necessary,
thus taking longer. If you notice at Oxford Street for example, it loads
each street 1 chunk ahead of where you are walking, and only once you walk
towards it. This appears seamless, but it is constantly loading and
unloading image blocks from memory - so it only ever loads what it needs to.
It's quite efficient and we're quite proud of the j/s code we developed
which interacts with the Google Maps interface. Getting Google Maps and all
affiliate links and banners to interact with Flash would *not*, we feel,
have been 'far better' :) Hope you can agree now we've clarified.

In article <4bd366e1-7bd1-41a5-b529-6dcc07cd815e [at] w28g2000hsf.googlegroups.com>, VK <schools_ring [at] yahoo.com> wrote:
>On Nov 17, 11:06 pm, VK <schools_r... [at] yahoo.com> wrote:
>> Then the KISS rules as usual I guess... :-)
>
>"KISS rulez" of course :-)
>
>P.S. KISS: a Silicon Valley programming community acronym staying from
>"Keep It Simple, Stupid"

Phooey. "KISS" is much, much older than the Silicon Valley programming
community.

--
Regards,
Doug Miller (alphageek at milmac dot com)

It's time to throw all their damned tea in the harbor again.

Mika wrote:

> Just as a point of interest, we chose HTML and j/s as the ability to add
> affiliates' HTML and j/s 'eposters' to shop windows, draw imagemaps around
> shop doors, and regularly update links etc. was much more straightforward if
> using the same language the actual links use.
>
> Also, loading the whole street first using Flash would have been necessary,
> thus taking longer.

No at Flash expert, maybe Travis can offer more precise info, but it is
my understanding that Flash can do sequential loading and that it would
not be necessary to load the whole shabang.

> If you notice at Oxford Street for example, it loads
> each street 1 chunk ahead of where you are walking, and only once you walk
> towards it. This appears seamless, but it is constantly loading and
> unloading image blocks from memory - so it only ever loads what it needs to.
> It's quite efficient and we're quite proud of the j/s code we developed
> which interacts with the Google Maps interface. Getting Google Maps and all
> affiliate links and banners to interact with Flash would *not*, we feel,
> have been 'far better' :) Hope you can agree now we've clarified.

Actually no I have no idea since I am stuck on dialup a webpage of a
*mere* 5-6mb is not quite accessible...

--
Take care,

Jonathan
-------------------
LITTLE WORKS STUDIO
http://www.LittleWorksStudio.com

On Sun, 18 Nov 2007 15:15:41 GMT, in comp.lang.javascript "Mika"
<anon [at] anon.com>
<xGY%i.49525$c_1.26385 [at] text.news.blueyonder.co.uk> wrote:

>| "Jeff North" <jnorthau [at] yahoo.com.au> wrote in message
>| news:j9ouj3hacf25adjjva1frldqklhv76fjo8 [at] 4ax.com...
>| > On Fri, 16 Nov 2007 18:12:37 GMT, in comp.lang.javascript "Mika"
>| > <anon [at] anon.com>
>| > <p4l%i.48642$c_1.38326 [at] text.news.blueyonder.co.uk> wrote:
>| >
>| >>| Hello, we understand you guys may be able to help.

[snip]

>| >>| Internet Explorer cannot open the Internet site...
>| >>| Operation aborted
>| >>|
>| >>| Here is an example of the page in question:
>| >>| http://tinyurl.com/35mwxr [broadband recommended]

[snip]

>| > I'd fix up the errors/warnings within the html first.
>| > -----------------------------------------------------
>| > Result: 0 errors / 139 warnings

[snip]

>| Thanks. There are no "errors" that we know of or can see, although there
>| are some warnings which do not affect the end result so can be ignored.
>|
>| However can you suggest what the correct Doctype string should be if not the
>| current one?:
>|
>| <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
>| "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
>| <html xmlns="http://www.w3.org/1999/xhtml">
>| <head>
>| <meta http-equiv="Content-Type" content="text/html; charset=windows-1252">

Don't use XHTML - http://hixie.ch/advocacy/xhtml
That would solve some of the problems.

If you are using Firefox then download the HTML Validator by Marc
Gueury, Web Developer by Chris Pederick and Firebug by Joe Hewitt
plugins. These 3 plugins are invaluable, IMHO, to assist in the
development of any website.

The problems that needs fixing are:
line 30 column 1 - Warning: discarding unexpected <head>: you've got 2
head tags on the page
Don't use the <font> tag it's been deprecated.
Don't allow Dreamweaver to set the styling names otherwise all sorts
of weird and wonderful things can occur. For example:

..style1, .style13, .style2 {
color: #0054C7;
}
..style2 {
color: #000000;
color: #0054C7;
font-family: Tahoma;
font-size: 11px;
margin-top: 4px;
}
..style2 {
color: #000000;
}
..style2, .style45 {
color: #000000;
}


a {
color: #0000FF;
}
a {
color: #FFFFFF;
color: #0000FF;
}
a, .style19, a {
color: #FFFFFF;
}

td {
color: #000000 padding: 0;
}
td {
color: #000000 color:#000 padding: 0;
}

The following items have errors:
..fill {
text-alight: right; --> should be align not alight
}
..style66 {
font-size: 1.51232e+034;
}
..style69 {
font-size: 1.51232e+034;
}
..style70 {
font-size: 1.51232e+034;
}
-- ------------------------------------------------------------ -
jnorthau [at] yourpantsyahoo.com.au : Remove your pants to reply
-- ------------------------------------------------------------ -

"Jeff North" <jnorthau [at] yahoo.com.au> wrote in message
news:sj81k3lssffkldlunpn1783ki11tgb70rj [at] 4ax.com...

> Don't use XHTML - http://hixie.ch/advocacy/xhtml
> That would solve some of the problems.

Thanks, have changed to loose HTML, although the problem with the IE bug is
already fixed.

> If you are using Firefox then download the HTML Validator by Marc
> Gueury, Web Developer by Chris Pederick and Firebug by Joe Hewitt
> plugins. These 3 plugins are invaluable, IMHO, to assist in the
> development of any website.
>
> The problems that needs fixing are:
> line 30 column 1 - Warning: discarding unexpected <head>: you've got 2
> head tags on the page

This is actually because SSI is including a top and bottom border, which
have their own <head> tags, so it appears more than once. Strange I know
but that's how it seems to do it.

Thanks for the other tips.

"Jeff North" <jnorthau [at] yahoo.com.au> wrote in message
news:sj81k3lssffkldlunpn1783ki11tgb70rj [at] 4ax.com...

> The following items have errors:
> .fill {
> text-alight: right; --> should be align not alight

Where on earth did you find that? Can't see it anywhere on the site and
have done a search operation too. :-S

On Mon, 19 Nov 2007 10:52:54 GMT, in comp.lang.javascript "Mika"
<anon [at] anon.com>
<aWd0j.49941$c_1.38422 [at] text.news.blueyonder.co.uk> wrote:

>| "Jeff North" <jnorthau [at] yahoo.com.au> wrote in message
>| news:sj81k3lssffkldlunpn1783ki11tgb70rj [at] 4ax.com...
>|
>| > The following items have errors:
>| > .fill {
>| > text-alight: right; --> should be align not alight
>|
>| Where on earth did you find that? Can't see it anywhere on the site and
>| have done a search operation too. :-S

It's not one of yours:
http://imawow.weather.com/web/common/header/stylesheet/wow.c ss
-- ------------------------------------------------------------ -
jnorthau [at] yourpantsyahoo.com.au : Remove your pants to reply
-- ------------------------------------------------------------ -

Gazing into my crystal ball I observed "Mika" <anon [at] anon.com> writing in
news:rHd0j.49933$c_1.35286 [at] text.news.blueyonder.co.uk:

>> The problems that needs fixing are:
>> line 30 column 1 - Warning: discarding unexpected <head>: you've got
>> 2 head tags on the page
>
> This is actually because SSI is including a top and bottom border,
> which have their own <head> tags, so it appears more than once.
> Strange I know but that's how it seems to do it.
>
>

Then change the include files so that content isn't in there anymore.
This is how I usually structure these things (ASP):

<% option explicit
thispage = "" 'the title of the page
thisurl = "" 'the page url
%>
<!--#include file="linkrel.asp"-->

Linkrel has the following structure:
Doctype
HTML
Beginning of Head
Title (uses the thispage variable)
Meta information (also uses thispage variable)
Stylesheet link
External js
Opens connection to the db
Include for master functions used throughout the site
then...

</head>
<body>
<!--#include file="h1_inc.asp"-->
h1_inc uses thispage variable eg:
<h1><%=thispage%></h1>

then...
<!--#include file="nav_inc.asp"-->
nav_inc has navigation and uses thisurl to determine if the
link should use the .thispage class.

then...
<div id="content">
Page content and other stuff

then...
<!--include file="footer_inc.asp"-->
footer_inc has copyright, legalese, etc., and links to less used
document, eg. privacy and accessibility statements, closes connection to
the db
and...
</div>
</body>
</html>

--
Adrienne Boswell at Home
Arbpen Web Site Design Services
http://www.cavalcade-of-coding.info
Please respond to the group so others can share

"Mika" <anon [at] anon.com> wrote in message
news:xEY%i.49522$c_1.36384 [at] text.news.blueyonder.co.uk...
>
> "Mika" <anon [at] anon.com> wrote in message
> news:p4l%i.48642$c_1.38326 [at] text.news.blueyonder.co.uk...
>> Hello, we understand you guys may be able to help.
>>
>> We have a page which has been working great for over a year and gets many
>> hits. However recently something got changed that we cannot seem to
>> find, and now *sometimes* if you refresh the page (generally while it is
>> still loading) in IE7, we get the popup window error:
>>
>> Internet Explorer cannot open the Internet site...
>> Operation aborted
>>
>> Here is an example of the page in question:
>> http://tinyurl.com/35mwxr [broadband recommended]
>>
>> We appreciate you may have other comments on the site such as the size of
>> the pages, however we are not looking to change that at present, with
>> faster broadband becoming more abundant. Search engine listings alert
>> the user that broadband is recommended for this technology.
>>
>> As we said, the site worked great, but for this unknown reason now needs
>> some sort of a tweak to fix. The changes we made before it happened were
>> related to the body tag but they have been completely undone yet the
>> issue remains :-S
>>
>> Thanks in advance to anyone able to find the cure for us to test.
>>
>> Regards,
>> Mika [at] SHS.com
>
> Well we just restored a backup of the site and noted that we had removed
> the following apparently redundant CSS:
>
> <style type="text/css">
> .style1 {
> text-align: left;
> }
> .style32 {
> text-align: center;
> }
> .style38 {
> text-align: center;
> }
> .style39 {
> color: #000000;
> }
> </style>
>
> Reinstating this seems to have fixed the IE bug! Can anyone get the
> 'Operation aborted' window to appear now by refreshing this page WHILST it
> is still working?
> http://tinyurl.com/35mwxr
>
> There was a mention to some style code in one of the fixes for this known
> IE bug. Anyway, it now appears to be resolved.
>
> Thanks for all the tips. Hopefully MS will fix the bug before even more
> programmers hate their browser, even if the majority of public don't.

Okay it turns out we jumped the gun as the problem is still happening,
albeit less often. It is completely random.

The only surefire workaround for this IE bug is to close the </body> tag
before the Google Maps code. BUT as stated that then messes up Firefox
interpreting the code.

Can anyone suggest another way to do this (which doesn't work)?:

<!--[if IE]></body><![endif]-->

Need something really simple please. KISS as you say.

Thanks.

Jeff North wrote:
>
> Don't use XHTML - http://hixie.ch/advocacy/xhtml
> That would solve some of the problems.
>
Personally, I prefer XHTML 1.0 over HTML 4.x because it is much easier
to ensure it is error-free. But that's a personal choice.

Mika wrote:
> "Mika" <anon [at] anon.com> wrote in message
>>> Internet Explorer cannot open the Internet site...
>>> Operation aborted
>> There was a mention to some style code in one of the fixes for this known
>> IE bug. Anyway, it now appears to be resolved.

No style problems can cause that. You've just shifted the problem around
a bit. Edit: I just read you're including google maps code, that'll be
what's doing it.

>> Thanks for all the tips. Hopefully MS will fix the bug before even more
>> programmers hate their browser, even if the majority of public don't.
> Okay it turns out we jumped the gun as the problem is still happening,
> albeit less often. It is completely random.

The problem is that some code is trying to dynamically create DOM
elements before the page is complete (i.e. before the </body> tag). IE
won't tolerate this.

> Can anyone suggest another way to do this (which doesn't work)?:
> <!--[if IE]></body><![endif]-->

Have you tried using document.write("<\/body>"); ?

If that doesn't work, then I'd just put the </body> tag inline as it
should be and deal with Firefox's problem. I haven't read all the posts
in this thread so I don't know details of what the problem is there.

On 19 Nov, 18:38, The Magpie <use... [at] pigsinspace.co.uk> wrote:

> Personally, I prefer XHTML 1.0 over HTML 4.x because it is much easier
> to ensure it is error-free. But that's a personal choice.

What makes you think that?


> [at] pigsinspace.co.uk

OMG! It's the uber-Mabbett!