Hi,

I coded a page and used &nbsp as a seperator for the images in a horizontal
navigation bar.

When I view the page in my bowser, IE throws an information bar up "to help
protect your security IE has restricted this webpage from running
scripts......."

Do I need to avoid &nbsp if I don't want my visitors to get the same ?

Is there some risk I should be aware of if I use &nbsp ?

--
Rich
http://www.richdavies.com

"Rich" <EMAIL REMOVED> wrote in message
news:EMAIL REMOVED...
> Hi,
>
> I coded a page and used &nbsp as a seperator for the images in a
> horizontal navigation bar.
>
> When I view the page in my bowser, IE throws an information bar up "to
> help protect your security IE has restricted this webpage from running
> scripts......."
>
> Do I need to avoid &nbsp if I don't want my visitors to get the same ?
>
> Is there some risk I should be aware of if I use &nbsp ?
>

Do you get the same problem if your replace it with   ?

Suddenly, without warning, Rich exclaimed (27-May-07 5:12 PM):
> Hi,
>
> I coded a page and used &nbsp as a seperator for the images in a horizontal
> navigation bar.
>
> When I view the page in my bowser, IE throws an information bar up "to help
> protect your security IE has restricted this webpage from running
> scripts......."
>
> Do I need to avoid &nbsp if I don't want my visitors to get the same ?
>
> Is there some risk I should be aware of if I use &nbsp ?
>
> --
> Rich
> http://www.richdavies.com
>
>
>
>
It's &nbsp; (semicolon at the end). Could that be your problem?

jmc

Rich wrote:
> Hi,
>
> I coded a page and used &nbsp as a seperator for the images in a horizontal
> navigation bar.

I hope you mean &nbsp;, including a semicolon. I'm sure you do. (And of
course, it's "separator".)

>
> When I view the page in my bowser, IE

LOL! Truer words were never spoken.

> throws an information bar up "to help
> protect your security IE has restricted this webpage from running
> scripts......."
>
> Do I need to avoid &nbsp if I don't want my visitors to get the same ?

If IE7 is so sensitive, that it wets its pants over non-breaking spaces,
then a lot of other sites will have problems too. IE7 would have died by
now.

What makes you think it's the &nbsp; and not your scripts?

>
> Is there some risk I should be aware of if I use &nbsp ?
>
> --

BTW: A real sig separator has a space following the two dashes.

> Rich
> http://www.richdavies.com/

Well, I have worse news for you than IE security restrictions. The above
page has no horizontal navigation bar whatsoever. For me, it's a
vertical nav bar (made with .jpgs and <br>s, naughty, naughty!) on the
left side.

If you are talking about a different page than the one here, please
provide the correct URL.

In any case, have you tested with a simplified case? E.g., does IE
complain when the page has &nbsp; but no JS?

--
John

>
> I hope you mean &nbsp;, including a semicolon. I'm sure you do. (And of
> course, it's "separator".)

Yes I do mean &nbsp;, thanks also for alerting me to to the typo in
separator.



>
> What makes you think it's the &nbsp; and not your scripts?

Because I had trouble identifying the root cause of the security message, I
ended up creating a page with only &nbsp; in the body, and thats how I know
it's definitely that.


>
> BTW: A real sig separator has a space following the two dashes.
>
>> Rich
>> http://www.richdavies.com/

noted. I'll fix that.


> Well, I have worse news for you than IE security restrictions. The above
> page has no horizontal navigation bar whatsoever. For me, it's a vertical
> nav bar (made with .jpgs and <br>s, naughty, naughty!) on the left side.
>
> If you are talking about a different page than the one here, please
> provide the correct URL.

I'm not talking about my personal site I use in my sig, I'm talking about a
page I'm working on for another site. I haven't uploaded it because it
failed my testing, so is local.

"Rich" <EMAIL REMOVED> wrote in message
news:EMAIL REMOVED...

>> I hope you mean &nbsp;, including a semicolon. I'm sure you do. (And of
>> course, it's "separator".)

> Yes I do mean &nbsp;, thanks also for alerting me to to the typo in
> separator.

>> What makes you think it's the &nbsp; and not your scripts?

> Because I had trouble identifying the root cause of the security message,
> I ended up creating a page with only &nbsp; in the body, and thats how I
> know it's definitely that.

&nbsp; with or without the ; has absolutely nothing to do with scripting,
javascript or any other flavour. It is an HTML entity, just like any other
HTML character, w for example. w, ' ', &nbsp;, &quot;.

It's like saying your car won't start because you have house number on your
front door.

You have something else wrong and it is not the &nbsp;.

> I'm not talking about my personal site I use in my sig, I'm talking about
> a page I'm working on for another site. I haven't uploaded it because it
> failed my testing, so is local.

Then put the offending page up on your personal site as a test page so we
can see it.

--
Richard.

Rich wrote:

> I'm not talking about my personal site I use in my sig, I'm talking about a
> page I'm working on for another site. I haven't uploaded it because it
> failed my testing, so is local.
>
IE is more picky about stuff on a local machine - upload it to an
unlinked directory and the problem (often) will go away.

HTH

--
TK
http://wejuggle2.com/
Still Having a Ball
celebrating 40,000 miles of running without getting "run-down"

----== Posted via Newsfeeds.Com - Unlimited-Unrestricted-Secure Usenet News==----
http://www.newsfeeds.com The #1 Newsgroup Service in the World! 120,000+ Newsgroups
----= East and West-Coast Server Farms - Total Privacy via Encryption =----

>
>>> I hope you mean &nbsp;, including a semicolon. I'm sure you do. (And of
>>> course, it's "separator".)
>
>> Yes I do mean &nbsp;, thanks also for alerting me to to the typo in
>> separator.
>
>>> What makes you think it's the &nbsp; and not your scripts?
>
>> Because I had trouble identifying the root cause of the security message,
>> I ended up creating a page with only &nbsp; in the body, and thats how I
>> know it's definitely that.
>
> &nbsp; with or without the ; has absolutely nothing to do with scripting,
> javascript or any other flavour. It is an HTML entity, just like any other
> HTML character, w for example. w, ' ', &nbsp;, &quot;.
>
> It's like saying your car won't start because you have house number on
> your front door.
>
> You have something else wrong and it is not the &nbsp;.
>
>> I'm not talking about my personal site I use in my sig, I'm talking about
>> a page I'm working on for another site. I haven't uploaded it because it
>> failed my testing, so is local.
>
> Then put the offending page up on your personal site as a test page so we
> can see it.
>
> --
> Richard.

Ever had a "Doh" moment ?

I uploaded the test file, it works fine on the web. So I took &nbsp; out of
the test file, and accessed the page locally.

IE again warned me. It's nothing to do with &nbsp; , simply IE warns when C:
is being accessed. Doh!!

--
Rich
http://www.richdavies.com

"Rich" <EMAIL REMOVED> wrote in message
news:EMAIL REMOVED...

>> You have something else wrong and it is not the &nbsp;.

> Ever had a "Doh" moment ?

Yep.

> I uploaded the test file, it works fine on the web. So I took &nbsp; out
> of the test file, and accessed the page locally.
>
> IE again warned me. It's nothing to do with &nbsp; , simply IE warns when
> C: is being accessed. Doh!!

Heh. Doh...

Never thought of the "mark of the web" (you didn't really give enough
information to spot it). Google for it :-)

Big Hint: Code to modern browsers, Firefox etc. Then test in IE. If IE fails
then the odds are it is a Microsoft problem.

--
Richard.

Rich wrote:
>
> Ever had a "Doh" moment ?

Usually no more than three times an hour...

>
> I uploaded the test file, it works fine on the web. So I took &nbsp; out of
> the test file, and accessed the page locally.
>
> IE again warned me. It's nothing to do with &nbsp; , simply IE warns when C:
> is being accessed. Doh!!

Don't say "doh;" say "aha!"

> --
> Rich

The space comes _after_. So (only) dash-dash-space-CR/LF.

Cheers.
--
John