</noedit> tag from Adobe GoLive ends a <div> tag

VERIFIED WORKSFORME

Status

()

Core
HTML: Parser
VERIFIED WORKSFORME
17 years ago
17 years ago

People

(Reporter: Andy Jones, Assigned: harishd)

Tracking

Trunk
PowerPC
Mac System 9.x
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

Attachments

(2 attachments)

(Reporter)

Description

17 years ago
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Macintosh; U; PPC; en-US; rv:0.9.3) Gecko/20010802
BuildID:    2001080214

When using Adobe GoLive there is a trick to keep the program from rewriting your
code. The trick it to put <noedit></noedit> tags around the part you want GoLive
to ignore. If you have code on your page like: "<noedit><div id="blah">text
text</noedit>text text</div>" Mozilla will read the </noedit> tag as </div>.
<noedit> is not compliant HTML but still should be ignored.

Reproducible: Always
Steps to Reproduce:
1. See description
2.
3.

Actual Results:  Page does not render correctly. text after </noedit> tag is out
of <div>

Expected Results:  Text should remain in <div> until </div> tag
(Assignee)

Comment 1

17 years ago
Created attachment 46939 [details]
Self explanatory test case
(Assignee)

Comment 2

17 years ago
This is fixed along with fix for bug 56245. Please try 08/23/01 build.
Marking WFM.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 17 years ago
Resolution: --- → WORKSFORME

Comment 3

17 years ago
The testcase is not well-formed.

Comment 4

17 years ago
Created attachment 46942 [details]
Testcase made valid and well-formed XHTML

Comment 5

17 years ago
By moving the opening <noedit> tag inside the div, the document becomes well-formed 
and works as expected. Making it XHTML makes the noedit tags acceptable.

I'm happy this edge case works now, but I'm lowering its' severity to enhancement 
anyway. There's no need to support weird markup like this when there's a perfectly 
simple workaround.
Severity: normal → enhancement
(Assignee)

Comment 6

17 years ago
Why are we worried about well-formedness here? The test case that I attached
will break when viewed using N6.1 but will render fine with 08/23/01 nightly.
Severity: enhancement → normal
(Assignee)

Comment 7

17 years ago
HTML == malformed. In XHTML the xml parser would have thrown an error.

Updated

17 years ago
QA Contact: bsharma → moied

Comment 8

17 years ago
Verified WFM
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.