Closed
Bug 890435
Opened 12 years ago
Closed 11 years ago
The width of <input> tag isn't affected by some css
Categories
(Core :: Layout, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: sheile1024, Unassigned)
Details
(Whiteboard: [dupeme])
Attachments
(2 files)
User Agent: Mozilla/5.0 (Windows NT 6.1; rv:23.0) Gecko/20100101 Firefox/23.0 (Beta/Release)
Build ID: 20130703181823
Steps to reproduce:
I want to expand width of <input> tag without width style and use below css.
Please open the attached reproduce.html in Firefox and Google Chrome.
------------------------------
.maxwidth {
display: block;
position: absolute;
left: 0px;
right: 0px;
background-color: #F99;
}
Actual results:
width of <a> tag expand correctly.
But, width of <input> tag isn't affected by same css.
I'll attach a capture image immediately when created this ticket.
Firefox(upper) screenshot in attached ff_and_chrome.png
Expected results:
All elements should expand width from same css.
I'll attach a capture image immediately when created this ticket.
See Google Chrome(lower) screenshot in attached ff_and_chrome.png
| Reporter | ||
Comment 1•12 years ago
|
||
Comment 2•12 years ago
|
||
I can confirm the behavior on FF as far back as FF10, though I'm sure it's older than that.
I can confirm that both Chrome and Safari draw the second element as wide as the first.
So, we should have a reason as to why Firefox differs. However, this is not new behavior.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Updated•12 years ago
|
Attachment #771535 -
Attachment mime type: text/plain → text/html
Updated•11 years ago
|
QA Whiteboard: [bugday-20140407]
Component: Untriaged → Layout
Product: Firefox → Core
Comment 4•11 years ago
|
||
> So, we should have a reason as to why Firefox differs.
Yes, because the spec says to do what we do.
The Safari behavior is covered by https://bugs.webkit.org/show_bug.cgi?id=81863
Chrome seems to be following the spec nowadays, like us and IE, though they also have <https://code.google.com/p/chromium/issues/detail?id=286679>.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•