- From: Daniel Holbert via GitHub <sysbot+gh@w3.org>
- Date: Wed, 10 Nov 2021 20:03:49 +0000
- To: public-css-archive@w3.org
Some observations: 1. it's not as simple as "Safari stretches buttons in both axes". They do that for literal `<button>` but they don't for any other button-like element. (They shrink input type="button/reset/submit" in the block axis, and they shrink input type="image" in both axes.) 2. Textfield-like elements are another related area where browsers disagree. Firefox does shrink-to-fit in both axes (except for `date` which we stretch in block axis); Chrome does shrink-to-fit in the inline axis only, and stretches in the block axis; Safari stretches in both axes. 3. input type="range" has the same behavior across the three engines (fully shrink-to-fit in Firefox; shrink-to-fit in inline axis in Chrome, fully-stretched in Safari) 4. All three browsers agree on shrink-to-fit for `<input>` with `type="color/checkbox/radio"`, and also for `<progress>`, and `<meter>`. 5. All three browsers agree on stretching for `<label>` and `<fieldset>`, and we nearly-agree for `<output>` (Chrome shrinks in the inline axis for that one so it's not full agreement). So: things are a bit of a mess, though (4) and (5) are the points of agreement. Ideally I'd like to have a coherent and likely-to-be-web-compatible way forward here, and I'm not sure that the proposed change (stretching in both axes) is that, given that there are a handful of button-like elements that no browser stretches in both axes at this point. -- GitHub Notification of comment by dholbert Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6789#issuecomment-965700501 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 10 November 2021 20:03:51 UTC