Closed
Bug 733914
Opened 12 years ago
Closed 7 years ago
<button> being treated as a replaced element (and <input type=button>, etc) means that one of 'left' and 'right' is ignored if both are set for an absolutely positioned button
Categories
(Core :: Layout: Form Controls, defect)
Core
Layout: Form Controls
Tracking
()
RESOLVED
INVALID
People
(Reporter: jmarston, Unassigned)
References
Details
Attachments
(2 files)
User Agent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; .NET4.0E; InfoPath.3; Zune 4.7) Steps to reproduce: I'm using Firefox 10.0.1 and I've found a bug regarding button elements that are absolutely positioned. The problem is setting both the right and left CSS attributes does not affect the width of the button as it should. I've attached a test case. In all other browsers the button is 500px wide, in Firefox it sizes to its content. Actual results: Firefox is not adjusting the width of an absolutely positioned button based on it's left and right CSS attributes Expected results: It should adjust the width according to the left and right CSS attributes.
|
||
Updated•12 years ago
|
Attachment #603873 -
Attachment mime type: text/plain → text/html
|
|
||
Comment 1•12 years ago
|
||
Confirmed on Mozilla/5.0 (Windows NT 5.1; rv:13.0) Gecko/20120307 Firefox/13.0a1 ID:20120307031051 IE and Safari do show the large 500px button, while Opera and Firefox do not.
Component: Untriaged → Layout
Product: Firefox → Core
QA Contact: untriaged → layout
Version: 10 Branch → Trunk
|
||
Comment 2•12 years ago
|
||
The correct rendering depends on whether a button is a replaced element or not. In Gecko and Presto it is, apparently. In Trident and WebKit it's not, apparently. The HTML spec does not define whether it's a replaced element or not, so both renderings are allowed by the spec....
Component: Layout → Layout: Form Controls
QA Contact: layout → layout.form-controls
Whiteboard: INVALID?
|
|
||
Updated•12 years ago
|
Summary: Rendering bug with absolutely positioned button tags → <button> being treated as a replaced element means that one of 'left' and 'right' is ignored if both are set for an absolutely positioned button
|
||
Updated•12 years ago
|
OS: Windows 7 → All
Hardware: x86_64 → All
|
||
Comment 3•8 years ago
|
||
Edge 13.10586 renders both <button> and <input type=button> the same (500px). Chrome and Firefox ignores 'right' and shrink-wraps the button text.
|
||
Comment 4•7 years ago
|
||
This was filed again recently as bug 1373351, FWIW. I closed that one as "invalid" (as it looks like bz was considering doing with the verison here, back in comment 2, per the whiteboard status added then). I'll update the other bug to be a dupe of this one, and close this one as invalid, I suppose. I also filed an issue to get this clarified in the HTML spec: https://github.com/whatwg/html/issues/2948
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
See Also: → https://github.com/whatwg/html/issues/2948
Whiteboard: INVALID?
|
|
||
Updated•7 years ago
|
Summary: <button> being treated as a replaced element means that one of 'left' and 'right' is ignored if both are set for an absolutely positioned button → <button> being treated as a replaced element (and <input type=button>, etc) means that one of 'left' and 'right' is ignored if both are set for an absolutely positioned button
You need to log in
before you can comment on or make changes to this bug.
Description
•