noframes tag implicitly ends p tag while noscript, nolayer, noembed tags do not

RESOLVED FIXED in mozilla1.9alpha1

Status

()

Core
HTML: Parser
P4
normal
RESOLVED FIXED
13 years ago
12 years ago

People

(Reporter: David D. Kilzer (ddk), Assigned: mrbkap)

Tracking

Trunk
mozilla1.9alpha1
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [patch], URL)

Attachments

(2 attachments)

(Reporter)

Description

13 years ago
The <noframes> tag implicitly ends a <p> tag, while the <noscript>, <nolayer> and <noembed> tags do not in Firefox 1.5.0.1.  This behavior differs from MSIE 6 in which none of the tags cause <p> to implicitly end.

See also this WebKit bug:  http://bugzilla.opendarwin.org/show_bug.cgi?id=7265
(Reporter)

Comment 1

13 years ago
Created attachment 211951 [details]
Test case v1
(Reporter)

Comment 2

13 years ago
Changing to HTML: Parser component per Maciej's suggestion.
Component: DOM: HTML → HTML: Parser
(Reporter)

Updated

13 years ago
Assignee: general → mrbkap
QA Contact: ian → parser
(Assignee)

Comment 3

13 years ago
Sure, why not?
Status: NEW → ASSIGNED
OS: MacOS X → All
Priority: -- → P4
Hardware: Macintosh → All
Target Milestone: --- → mozilla1.9alpha
I don't have a strong oppinion either way on this.
(Assignee)

Comment 5

12 years ago
Created attachment 215802 [details] [diff] [review]
Allow inlines to contain noframes

fwiw, the old behavior isn't totally out the window, but this seems like an easy interoperability win.
Attachment #215802 - Flags: superreview?(jst)
Attachment #215802 - Flags: review?(jst)
(Assignee)

Updated

12 years ago
Whiteboard: [patch]
Comment on attachment 215802 [details] [diff] [review]
Allow inlines to contain noframes

r+sr=jst
Attachment #215802 - Flags: superreview?(jst)
Attachment #215802 - Flags: superreview+
Attachment #215802 - Flags: review?(jst)
Attachment #215802 - Flags: review+
(Assignee)

Comment 7

12 years ago
Fix checked into trunk.
Status: ASSIGNED → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.