DW and FW menus blocked by IE

[antirev]

Being enticed to use Dreamweaver and Fireworks as my wysiwyg editors, in part,
because of the ease at which navigation bars with pull-down menus can be
created, I was surprised to see that the function of these menus were blocked
by the firewall in Internet Explorer when I attempted to test them. Only once I
had selected to accept the danger of running scripts on the page was I able to
view the full function of my nav bar. I thought Macromedia was cross-browser
compatible. Did I do something wrong? If I did, I didn't see any options before
testing. Is it because javacript is being used by Fireworks and Dreamweaver to
create the properties which isn't supported any more by Microsoft? Should I
switch to another program to create my menus or is there another answer?

[Heather]

This will explain IE blocking active content.

[url]http://www.projectseven.com/support/answers.asp?id=153[/url]

And once you've read that, you should know that the DW and FW pop-up menus
create more problems than they're worth and in the end, there are better and
easier ways to create your own pop-up/flyout/drop-down menu...

Read these to learn more:

[url]http://www.apptools.com/rants/jsmenu.php[/url]
[url]http://www.apptools.com/rants/menus.php[/url]


--
Heather



"antirev" <webforumsuser@macromedia.com> wrote in message
news:cv8jqu$8kp$1@forums.macromedia.com...

> Being enticed to use Dreamweaver and Fireworks as my wysiwyg editors, in
> part,
> because of the ease at which navigation bars with pull-down menus can be
> created, I was surprised to see that the function of these menus were
> blocked
> by the firewall in Internet Explorer when I attempted to test them. Only
> once I
> had selected to accept the danger of running scripts on the page was I
> able to
> view the full function of my nav bar. I thought Macromedia was
> cross-browser
> compatible. Did I do something wrong? If I did, I didn't see any options
> before
> testing. Is it because javacript is being used by Fireworks and
> Dreamweaver to
> create the properties which isn't supported any more by Microsoft? Should
> I
> switch to another program to create my menus or is there another answer?
>

[Murray *TMM*]

Wait until you read this -

[url]http://apptools.com/rants/jsmenu.php[/url]
[url]http://apptools.com/rants/menus.php[/url]

And definitely do not use DW/FW for their pop-up menus. There are sooooo
many other things about them to love....

--
Murray --- ICQ 71997575
Team Macromedia Volunteer for Dreamweaver
(If you *MUST* email me, don't LAUGH when you do so!)
==================
[url]http://www.dreamweavermx-templates.com[/url] - Template Triage!
[url]http://www.projectseven.com/go[/url] - DW FAQs, Tutorials & Resources
[url]http://www.dwfaq.com[/url] - DW FAQs, Tutorials & Resources
[url]http://www.macromedia.com/support/search/[/url] - Macromedia (MM) Technotes
==================

"antirev" <webforumsuser@macromedia.com> wrote in message
news:cv8jqu$8kp$1@forums.macromedia.com...

> Being enticed to use Dreamweaver and Fireworks as my wysiwyg editors, in
> part,
> because of the ease at which navigation bars with pull-down menus can be
> created, I was surprised to see that the function of these menus were
> blocked
> by the firewall in Internet Explorer when I attempted to test them. Only
> once I
> had selected to accept the danger of running scripts on the page was I
> able to
> view the full function of my nav bar. I thought Macromedia was
> cross-browser
> compatible. Did I do something wrong? If I did, I didn't see any options
> before
> testing. Is it because javacript is being used by Fireworks and
> Dreamweaver to
> create the properties which isn't supported any more by Microsoft? Should
> I
> switch to another program to create my menus or is there another answer?
>

[Murray *TMM*]

Oops - didn't see your comprehensive post, Heather. Sorry for the
duplication!

--
Murray --- ICQ 71997575
Team Macromedia Volunteer for Dreamweaver
(If you *MUST* email me, don't LAUGH when you do so!)
==================
[url]http://www.dreamweavermx-templates.com[/url] - Template Triage!
[url]http://www.projectseven.com/go[/url] - DW FAQs, Tutorials & Resources
[url]http://www.dwfaq.com[/url] - DW FAQs, Tutorials & Resources
[url]http://www.macromedia.com/support/search/[/url] - Macromedia (MM) Technotes
==================

"Heather" <info@NOJUNKfeathertheweb.com> wrote in message
news:cv8kmv$9p2$1@forums.macromedia.com...

> This will explain IE blocking active content.
>
> [url]http://www.projectseven.com/support/answers.asp?id=153[/url]
>
> And once you've read that, you should know that the DW and FW pop-up menus
> create more problems than they're worth and in the end, there are better
> and easier ways to create your own pop-up/flyout/drop-down menu...
>
> Read these to learn more:
>
> [url]http://www.apptools.com/rants/jsmenu.php[/url]
> [url]http://www.apptools.com/rants/menus.php[/url]
>
>
> --
> Heather
>
>
>
> "antirev" <webforumsuser@macromedia.com> wrote in message
> news:cv8jqu$8kp$1@forums.macromedia.com...

>> Being enticed to use Dreamweaver and Fireworks as my wysiwyg editors, in
>> part,
>> because of the ease at which navigation bars with pull-down menus can be
>> created, I was surprised to see that the function of these menus were
>> blocked
>> by the firewall in Internet Explorer when I attempted to test them. Only
>> once I
>> had selected to accept the danger of running scripts on the page was I
>> able to
>> view the full function of my nav bar. I thought Macromedia was
>> cross-browser
>> compatible. Did I do something wrong? If I did, I didn't see any options
>> before
>> testing. Is it because javacript is being used by Fireworks and
>> Dreamweaver to
>> create the properties which isn't supported any more by Microsoft? Should
>> I
>> switch to another program to create my menus or is there another answer?
>>

>
>

[Heather]

No worries...maybe the information will sink in more than it would with just
one reply. :)

--
Heather



"Murray *TMM*" <forums@HAHAgreat-web-sights.com> wrote in message
news:cv8m2v$b67$1@forums.macromedia.com...

> Oops - didn't see your comprehensive post, Heather. Sorry for the
> duplication!
>
> --
> Murray --- ICQ 71997575
> Team Macromedia Volunteer for Dreamweaver
> (If you *MUST* email me, don't LAUGH when you do so!)
> ==================
> [url]http://www.dreamweavermx-templates.com[/url] - Template Triage!
> [url]http://www.projectseven.com/go[/url] - DW FAQs, Tutorials & Resources
> [url]http://www.dwfaq.com[/url] - DW FAQs, Tutorials & Resources
> [url]http://www.macromedia.com/support/search/[/url] - Macromedia (MM) Technotes
> ==================
>
> "Heather" <info@NOJUNKfeathertheweb.com> wrote in message
> news:cv8kmv$9p2$1@forums.macromedia.com...

>> This will explain IE blocking active content.
>>
>> [url]http://www.projectseven.com/support/answers.asp?id=153[/url]
>>
>> And once you've read that, you should know that the DW and FW pop-up
>> menus create more problems than they're worth and in the end, there are
>> better and easier ways to create your own pop-up/flyout/drop-down menu...
>>
>> Read these to learn more:
>>
>> [url]http://www.apptools.com/rants/jsmenu.php[/url]
>> [url]http://www.apptools.com/rants/menus.php[/url]
>>
>>
>> --
>> Heather
>>
>>
>>
>> "antirev" <webforumsuser@macromedia.com> wrote in message
>> news:cv8jqu$8kp$1@forums.macromedia.com...

>>> Being enticed to use Dreamweaver and Fireworks as my wysiwyg editors, in
>>> part,
>>> because of the ease at which navigation bars with pull-down menus can be
>>> created, I was surprised to see that the function of these menus were
>>> blocked
>>> by the firewall in Internet Explorer when I attempted to test them. Only
>>> once I
>>> had selected to accept the danger of running scripts on the page was I
>>> able to
>>> view the full function of my nav bar. I thought Macromedia was
>>> cross-browser
>>> compatible. Did I do something wrong? If I did, I didn't see any options
>>> before
>>> testing. Is it because javacript is being used by Fireworks and
>>> Dreamweaver to
>>> create the properties which isn't supported any more by Microsoft?
>>> Should I
>>> switch to another program to create my menus or is there another answer?
>>>

>>
>>

>
>

[Heather]

> And definitely do not use DW/FW for their pop-up menus. There are sooooo

> many other things about them to love....

Or not to love... ;-)

--
Heather



"Murray *TMM*" <forums@HAHAgreat-web-sights.com> wrote in message
news:cv8m1p$b5m$1@forums.macromedia.com...

> Wait until you read this -
>
> [url]http://apptools.com/rants/jsmenu.php[/url]
> [url]http://apptools.com/rants/menus.php[/url]
>

>
> --
> Murray --- ICQ 71997575
> Team Macromedia Volunteer for Dreamweaver
> (If you *MUST* email me, don't LAUGH when you do so!)
> ==================
> [url]http://www.dreamweavermx-templates.com[/url] - Template Triage!
> [url]http://www.projectseven.com/go[/url] - DW FAQs, Tutorials & Resources
> [url]http://www.dwfaq.com[/url] - DW FAQs, Tutorials & Resources
> [url]http://www.macromedia.com/support/search/[/url] - Macromedia (MM) Technotes
> ==================
>
> "antirev" <webforumsuser@macromedia.com> wrote in message
> news:cv8jqu$8kp$1@forums.macromedia.com...

>> Being enticed to use Dreamweaver and Fireworks as my wysiwyg editors, in
>> part,
>> because of the ease at which navigation bars with pull-down menus can be
>> created, I was surprised to see that the function of these menus were
>> blocked
>> by the firewall in Internet Explorer when I attempted to test them. Only
>> once I
>> had selected to accept the danger of running scripts on the page was I
>> able to
>> view the full function of my nav bar. I thought Macromedia was
>> cross-browser
>> compatible. Did I do something wrong? If I did, I didn't see any options
>> before
>> testing. Is it because javacript is being used by Fireworks and
>> Dreamweaver to
>> create the properties which isn't supported any more by Microsoft? Should
>> I
>> switch to another program to create my menus or is there another answer?
>>

>
>

[antirev]

Sorry , I've been away. Thanks Heather for the good information. I feel a lot better, now.