Bug 269169
| Summary: | Investigate field-sizing: content interaction with size containment | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Luke Warlow <lwarlow> |
| Component: | CSS | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Bug Depends on: | 269124, 269125 | ||
| Bug Blocks: | 264720 | ||
Luke Warlow
If you load `data:text/html,<select style="field-sizing:content;contain:size;"><option>option 1</option><option>really long option awdaadwadw</option></select>`, `data:text/html,<textarea style="field-sizing: content; contain:size;">long content</textarea>`, or `data:text/html,<input style="field-sizing: content; contain:size;" value="longcontent">` you'll see there's serious usability issues with size containment mixed with `field-sizing: content`.
This issue is to track investigating what the expected behaviour is and adjust the implementations to match that along with adding any tests that might be needed.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Luke Warlow
Based on the answer provided in https://issues.chromium.org/issues/324585426 WebKit should just ensure that it's consistent with Chromium in its behaviour.
Radar WebKit Bug Importer
<rdar://problem/123186769>