Dreamweaver rewriting spry:if statements

Question

I keep having a problem with Dreamweaver rewriting manually
created Spry select list code.
Example of the code as it should be:
<select name="orgSelect" id="orgSelect"
onchange="document.forms['frmSupportReq'].groupSelect.disabled =
true;dsOrg.setCurrentRowNumber(this.selectedIndex);"
spry:repeatchildren="dsOrg">
<option spry:if="{ds_RowNumber} == {ds_CurrentRowNumber}"
value="{name}" selected="selected">{name}</option>
<option spry:if="{ds_RowNumber} != {ds_CurrentRowNumber}"
value="{name}">{name}</option>
</select>
Dreamweaver rewrites it, breaking it (below is a sample of
the most recent break):
<select name="orgSelect" id="orgSelect"
onchange="document.forms['frmSupportReq'].groupSelect.disabled =
true;dsOrg.setCurrentRowNumber(this.selectedIndex);"
spry:repeatchildren="dsOrg">
<option spry:if="{dsOrg::ds_RowNumber} ==
{dsOrg::ds_CurrentRowNumber}" value="{dsOrg::name}"
selected="selected">{dsOrg::name}</option>
<option spry:if="{ds_RowNumber} != {ds_CurrentRowNumber}"
value="{name}">{name}</option>
</select>
Dreamweaver has rewritten the code in several different ways
over the last two days for this particular item (which is the first
part of a master/detail double select set).
This is getting very irritating.
Has anyone else had a similar problem? If so, has anyone
found a way to STOP Dreamweaver from breaking the Spry code?
I would appreciate suggestions on how to break Dreamweaver of
this annoying habit.
Thanks.
Skip Keats

Answer 1

Donald:
I am not certain if I can 'reproduce' it, per se, as the
occurrences do not follow any particular pattern, except what
Dorfadobe notes -- switching between code/split and design views.
All pages have at least one Spry-generated select list (used
as a jump menu). Many have more. The code noted above is part of an
actual form (rather than a jump menu system).
What I have noticed is that Dreamweaver does not seem to
change any code created by itself from design view. It only seems
to change code that is manually created in code view. (On a
separate note, it keeps trying to delete conditional validation
that I am creating for the same form -- you know, 'if yes, then
this field is available (and must validate)' type thing.
My question: Could it be that Dreamweaver is somehow
internally programmed to force conformance to its design view
'widgets' in some way? If so, this is a serious problem as the
widgets are rather limited in comparison to what can be done via
hand-coding.
Skip Keats