This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 20465 - input controls styling should apply box-sizing even in standards mode
Summary: input controls styling should apply box-sizing even in standards mode
Status: RESOLVED WORKSFORME
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: All All
: P3 normal
Target Milestone: ---
Assignee: This bug has no owner yet - up for the taking
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-12-20 17:35 UTC by Adrian Bateman [MSFT]
Modified: 2013-01-22 04:59 UTC (History)
4 users (show)

See Also:


Attachments
Standards mode test case (777 bytes, text/html)
2012-12-20 17:35 UTC, Adrian Bateman [MSFT]
Details
Quirks mode test case (757 bytes, text/html)
2012-12-20 17:35 UTC, Adrian Bateman [MSFT]
Details

Description Adrian Bateman [MSFT] 2012-12-20 17:35:16 UTC
Created attachment 1298 [details]
Standards mode test case

http://www.w3.org/TR/html5/rendering.html#form-controls

Currently the spec says that the following style should only be applied in quirks mode:

input { box-sizing: border-box; }

It appears that many browsers apply this in standards mode too. IE10 follows the spec and only applies this in quirks mode but we've found a live site that depends on this in standards mode and has a workaround coded for IE.

We propose that the spec should be updated to reflect what browsers do today and we intend to update IE's behaviour to match other browsers (i.e. apply this rule in both quirks and standards mode).

Currently this is likely to block CR since there will not be two interoperable implementations.
Comment 1 Adrian Bateman [MSFT] 2012-12-20 17:35:48 UTC
Created attachment 1299 [details]
Quirks mode test case
Comment 2 Adrian Bateman [MSFT] 2013-01-22 04:59:33 UTC
It turns out that we overlooked the text that scoped box-sizing:border-box to specific values of the "type" attribute when in standards mode, so the spec is correct.