-webkit-appearance:fieldset-legend considered harmful
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- css, html
- Domain
- frontend
Research direction
Start with the linked HTML rendering section and the issue's example showing -webkit-appearance on form controls. Review how the rendered legend behavior is specified and evaluate the proposed separation into a dedicated property. Done means the specification has an agreed, unambiguous direction for triggering rendered legend layout without changing themed control appearance.
Written by the indexing model from the issue text.
Description
https://whatpr.org/html/3934/rendering.html#the-fieldset-and-legend-elements
The child's used value of '-webkit-appearance' is 'fieldset-legend'.
Using -webkit-appearance to trigger the special rendered legend layout has the side-effect that it resets the themed appearance that some form controls have by default. For example,
<fieldset>
<input type=button style="-webkit-appearance:fieldset-legend" value="button">
<input type=button value="button">
</fieldset>
renders as (screenshot from my prototype implementation of -webkit-appearance:fieldset/fieldset-legend in Gecko):
I think that some of the HTML form control elements could be useful as a rendered legend so I think -webkit-appearance is not the right property to use for this. I think it would be better to mint a new CSS property to trigger the rendered legend layout, something like legend:auto|none. Then there is no risk of it affecting the default appearance of the element the author chooses to use as the rendered legend.
- Dominant language
- HTML
- Stars
- 9.4k
- Forks
- 3.2k
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 38
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from whatwg/html
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
topic: media topic: rendering
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
-
clarification
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
compat topic: navigation topic: navigation API
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
tvOS
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
bvaughn/react-resizable-panels#751 · 1 comment ·
-
www.wiwo.de OpenN: AdGuard Browser Extension P3: Medium T: Annoyance
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
AdguardTeam/AdguardFilters#242026 ·
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 92/100