Bug 13041

Summary: Form input and pieces misplaced in CSS3 columns
Product: WebKit Reporter: Matt Lilek <dev+webkit>
Component: Layout and RenderingAssignee: Nobody <webkit-unassigned>
Status: RESOLVED FIXED    
Severity: Normal CC: ddkilzer, hyatt, mitz
Priority: P2 Keywords: HasReduction
Version: 523.x (Safari 3)   
Hardware: Mac   
OS: OS X 10.4   
Attachments:
Description Flags
Testcase
none
Testcase with more form elements none

Matt Lilek
Reported 2007-03-10 18:40:50 PST
Load the attached testcase and type something in the input in the second column. The text will be garbled and placed below the first column.
Attachments
Testcase (328 bytes, text/html)
2007-03-10 18:42 PST, Matt Lilek 		no flags
Details
Testcase with more form elements (952 bytes, text/html)
2007-03-10 22:52 PST, Matt Lilek 		no flags
Details
Show Obsolete (1) View All Add attachment proposed patch, testcase, etc.
Matt Lilek
Comment 1 2007-03-10 18:42:29 PST
Created attachment 13582 [details] Testcase
Matt Lilek
Comment 2 2007-03-10 19:07:00 PST
This affects many form widgets, though I suppose this is covered under the original blog post on the feature with "At this time any stacking context children like relative positioned content or content that uses opacity will position impoperly (as though the column didn’t exist)" (one of these day's I'll learn to read...)
David Kilzer (:ddkilzer)
Comment 3 2007-03-10 21:29:55 PST
This definitely needs to be fixed before releasing Safari. Changing to P1 and adding NeedsRadar keyword.
Matt Lilek
Comment 4 2007-03-10 22:52:24 PST
Created attachment 13584 [details] Testcase with more form elements Expanded testcase with more form elements. If you remove the padding on the columns, the selects behave properly.
mitz
Comment 5 2007-03-10 22:54:07 PST
Layers ignore columns.
Dave Hyatt
Comment 6 2007-03-10 22:58:40 PST
The columns spec is probably going to change completely before it's released (people are actively proposing different syntax etc. in the WG right now). I'm not sure why this needs to be P1.
David Kilzer (:ddkilzer)
Comment 7 2007-03-11 09:53:31 PDT
(In reply to comment #6) > The columns spec is probably going to change completely before it's released > (people are actively proposing different syntax etc. in the WG right now). I'm > not sure why this needs to be P1. I marked it P1 because it just looks really, really bad. Have you tried typing in the right-hand text box in the first test case (Attachment 13582 [details])? Unless column support is going to be removed as part of the stabilization spree, I think this should be fixed. Obviously, that's just my opinion.
Maciej Stachowiak
Comment 8 2007-03-13 11:05:38 PDT
Something that looks really bad but is based on a relatively new experimental feature is not a P1. It would be nice to fix, but isn't a showstopper problem like a crash or hang or regression.
Dave Hyatt
Comment 9 2009-03-03 12:28:00 PST
Fixed when I added self-painting overflow layers.
Note You need to log in before you can comment on or make changes to this bug.