Bug 120465 - Button inputs do not follow the rules for replaced absolutely positioned elements correctly
Summary: Button inputs do not follow the rules for replaced absolutely positioned elem...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Forms (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL: data:text/html,<input type="button" s...
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-29 05:49 PDT by Boris Zbarsky
Modified: 2022-09-18 03:34 PDT (History)
5 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Boris Zbarsky 2013-08-29 05:49:02 PDT 
Consider the testcase in the url field.  In WebKit this renders with the input stretching the full width of the viewport.  Per CSS 2.1 section 10.3.8, the width should be the width a text input would normally have (rule 1 in 10.3.8), and the 'right' value should be ignored because the values are over-constrained (rule 6 in 10.3.8).

WebKit gets this right for images, but not for button inputs.

Gecko, Presto, and Trident all do this right last I checked.
Comment 1 Boris Zbarsky 2013-08-29 05:53:23 PDT 
> the width should be the width a text input would normally have

I meant a button input.
Comment 2 Ahmad Saleem 2022-09-18 03:34:19 PDT 
Test Case from URL field - https://jsfiddle.net/yw7391fk/show

Safari Technology Preview 153 and Chrome Canary 108 behave same and extend the input button field to full width of viewport while Firefox Nightly 106 does not extend it at all.

I think it should be in RADAR. Thanks!