Re: New Dreamweaver Bug...

Nope. I think you have other problems on your page. Or maybe I'm not
understanding your setup here.

To remove it (for
accessibility)

Why for accessibility?

--
Murray --- ICQ 71997575
Team Macromedia Volunteer for Dreamweaver MX
(If you *MUST* email me, don't LAUGH when you do so!)
==================
news://forums.macromedia.com/macromedia.dreamweaver - THE BEST WAY TO GET
ANSWERS
==================
http://www.dreamweavermx-templates.com - Template Triage!
http://www.projectseven.com/go - DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs, Tutorials & Resources
http://www.macromedia.com/support/search/ - Macromedia (MM) Technotes
==================

"Stevie_R" <webforumsuser (AT) macromedia (DOT) com> wrote

We appear to have found a new bug in DW MX 2004. Let's say you are using
a
template. And you want to do a find/replace on code for a special
character--&nbsp; for example, or &quot;

If you do a "find" on the source code, open the page, and then try to
change
it by hand (deleting the &nbsp; from code view for example), DW tells you
that
you are making changes to a region that is not editable, even when it is
clearly an editable region. It will also not allow you to keep the changes
even
temporarily. "Do you want to retain the changes until then?" If you
answer
yes, your changes are still discarded.

This has become a real issue with the &quot; code, as DW uses that code
any
time a quote is typed--no matter what your preferences say. To remove it
(for
accessibility), you need to put a quote in the source code--and once
you've
found them, you can't change them. Our fix so far is that we don't open
the
files that are being changed. We're changing them while they are closed,
and
hoping for the best.

Hopefully, they're working on this issue. Anyone else run into this? Any
other
fixes?

Thanks,
Stevie

Hi again, Murray.

First, let me just say thanks for all the time you've spent on this. My
understanding from our IT/Accessibility guru is that we are to limit as best we
can the number of &amp whatever; type codes we have in our pages. Some screen
readers don't render the code appropriately (that really bugs me, too) and so
for text like:

"Welcome," he said.
They read,

And quot semi-colon. Welcome comma and quot he said.

So we've been trying to avoid the &amp; quot; code. What I don't get is why DW
inserts it in the first place, especially when it's not needed and you haven't
asked it to... Straight quotes would seem to work just fine...

Unless we in my office are behind (again) and the &amp; quot; thing is no
longer an accessibility issue...

Stevie

Follow-up on prior note. We checked into the accessibility of "&quot" as a tag, and found that it's been supported since HTML 2.0--so is probably pretty safe to use. Whew!

Yes - that is good news. It's always safe to choose processes based on
information and facts rather than recollection! 8)

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

"Stevie_R" <webforumsuser (AT) macromedia (DOT) com> wrote

Follow-up on prior note. We checked into the accessibility of "&quot" as a
tag, and found that it's been supported since HTML 2.0--so is probably

pretty safe to use. Whew!