Closed
Bug 74857
Opened 23 years ago
Closed 21 years ago
span bg color is drawn over form controls
Categories
(Core :: Layout, defect, P2)
Tracking
()
RESOLVED
WORKSFORME
mozilla1.2alpha
People
(Reporter: scottputterman, Assigned: attinasi)
References
()
Details
Attachments
(2 files, 2 obsolete files)
20010404 on Win 2000. When I go to the above url, the page doesn't layout correctly. All of the edit fields are really small (luckily you can still type in them), you can't see the drop down arrows in the dropdowns and the buttons don't show up. However, if you do a reload, everything comes out fine.
Comment 2•23 years ago
|
||
changing summary and reassigning
Assignee: rods → attinasi
Summary: America West page doesn't layout correctly → span bg color is drawn over form controls
Comment 3•23 years ago
|
||
Comment 4•23 years ago
|
||
In the simple, testcase remove the background-color from the style rule and it will render fine.
Comment 5•23 years ago
|
||
Reporter | ||
Comment 6•23 years ago
|
||
nominating with various keywords. I think this is a pretty major page to have working.
Assignee | ||
Comment 7•23 years ago
|
||
I see the same behavior in NS6.01 too, btw. Will investigate, but I'm swamped for 0.9 right now.
Status: NEW → ASSIGNED
Assignee | ||
Comment 8•23 years ago
|
||
OK, this looks like yet another form-control in an inline problem (we are accumulating a lot of these). The same problem occurs for input, textarea dna button. It is all ok in a block (including a FORM), but not in an inline container, like a span. I think that Rod and I will have to work out something so that form controls can handle being put into inlines - right now they are very confused by inline containers. Assigning mozilla 0.9.1 milestone
Priority: -- → P2
Target Milestone: --- → mozilla0.9.1
Assignee | ||
Comment 9•23 years ago
|
||
Moving P2 and P3 bugs to 0.9.2
Target Milestone: mozilla0.9.1 → mozilla0.9.2
Assignee | ||
Comment 10•23 years ago
|
||
by mandate, moving non-crashers and non-datalossers outward.
Target Milestone: mozilla0.9.2 → mozilla0.9.3
Updated•23 years ago
|
Target Milestone: mozilla0.9.3 → mozilla0.9.4
Assignee | ||
Updated•23 years ago
|
Target Milestone: mozilla0.9.4 → mozilla1.0
Updated•23 years ago
|
Target Milestone: mozilla1.0 → mozilla1.2
Comment 11•23 years ago
|
||
I made one simple testcase like that: <style> SPAN.pull { BACKGROUND: red } SPAN.pull SELECT { BACKGROUND: blue } </STYLE> <span class=pull> <select name=productList> <option selected value=#>SELECT A TOPIC<option> <option selected value=#>SELECT A TOPIC<option> </select> </span>
Comment 12•22 years ago
|
||
See the button there, the span's color is on top of the button
Comment 13•22 years ago
|
||
Maybe html.css forgot to add display attribute of span...
Comment 14•22 years ago
|
||
dbaron: Could this bug related to the fix of bug 36710? I can't find your patch on bug 36710. Need your help. Thanks!
This does have to do with paint layers, but there are a bunch of other bugs on different form controls (some of which have been fixed), all of which really need to be fixed. See bug 107244, which fixed this problem for text inputs, radio buttons, and checkboxes.
Comment on attachment 76985 [details] [diff] [review] patch to fix html.css This patch is wrong.
Attachment #76985 -
Attachment is obsolete: true
Attachment #76985 -
Flags: needs-work+
Comment 17•22 years ago
|
||
I guess the following code points to a similar problem: <span style="color: #B69249;background-color: #BAFF52;"> abc <ul><li>uvw</li></ul> xyz</span> Probably either the background of the li is green to, or the font-color of the li should also be set back to the default (i.e. black)... http://bugzilla.mozilla.org/show_bug.cgi?id=156653 appears to be a similar problem
Updated•21 years ago
|
Attachment #29925 -
Attachment is obsolete: true
Comment 18•21 years ago
|
||
I'm not able to reproduce this bug.... is this still a problem?
Comment 19•21 years ago
|
||
No response == marking worksforme. Please reopen if this is still an issue.
Status: ASSIGNED → RESOLVED
Closed: 21 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•