[BLOCK] Form tags within a DIV will add extra space

VERIFIED FIXED in M16

Status

()

Core
Layout
P3
normal
VERIFIED FIXED
19 years ago
18 years ago

People

(Reporter: Michael Kay, Assigned: buster)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

19 years ago
I'm using M10 and I placed a form within a DIV. By default, the form tag is adding space

above the content of the form. See the URL mentioned in this ticket

Updated

19 years ago
Assignee: troy → kipp
(Reporter)

Updated

18 years ago
OS: Mac System 8.6 → All
Hardware: Macintosh → All
(Reporter)

Comment 1

18 years ago
This is occuring in M12 as well.

Comment 2

18 years ago
Updating to default Layout Assignee...kipp no longer with us :-(

Comment 3

18 years ago
Why are you re-reassing layout bugs? Do NOT touch layout bugs.

The bugs are assigned to Kipp so they can stay neatly organized until we have a
new owner for the block/inline code.
(Assignee)

Comment 4

18 years ago
mass moving all Kipp's pre-beta bugs to M15.  Nisheeth and I will
prioritize these and selectively move high-priority bugs into M13 and M14.
(Assignee)

Updated

18 years ago
Summary: Form tags within a DIV will add extra space → [BLOCK] Form tags within a DIV will add extra space

Comment 5

18 years ago
mike, could you look at this again with a recent build? It looks

ok to me. I think your bug may have been fixed. I'm using a build

I compiled this morning. You can get a recent build from

http://ftp.mozilla.org/pub/mozilla/nightly/latest/ or wait for M14

(Reporter)

Comment 6

18 years ago
Right on! It looks like it was fixed already in M13 and still good in M14. 

Comment 7

18 years ago
assigning to buster for triage since it looks like this bug is fixed
Assignee: kipp → buster

Comment 8

18 years ago
moving all buster m15 bugs to m16.
Target Milestone: M15 → M16
(Assignee)

Comment 9

18 years ago
I believe this already has been fixed.
Status: NEW → RESOLVED
Last Resolved: 18 years ago
Resolution: --- → FIXED

Comment 10

18 years ago
Fixed in the July 6th build.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.