New issue
Advanced search Search tips

Issue 679713 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Jan 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Fieldset's legend is rendered in a way that cannot be achieved via CSS

Reported by teo8...@gmail.com, Jan 10 2017

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36

Example URL:
http://jsbin.com/rubeqeviqo/edit?html,css,output

Steps to reproduce the problem:
1. visit http://output.jsbin.com/yuxekidanu
2. open the development tools, inspect the fieldset and the legend element, look at the style, specifically the style applied from "useragent stylesheet"
3. visit http://jsbin.com/rubeqeviqo/

What is the expected behavior?
ALL the style rules that were listed in the first example as being applied to the fieldset and legend elements, from user-agent stylesheet, have been copied to the "fieldset" and "legend" classes in the second example. Hence, by definition, the second example should look exactly the same as the first.

What went wrong?
The second example doesn't achieve the special positioning of the legend across the top border of the fieldset and interrupting the border. Of course you wouldn't expect that css code to achieve that, but that's the issue. 

EITHER 
there's no way to achieve that effect via pure CSS (either standard or via -webkit-whatever properties), which is fundamentally wrong as there shouldn't exist ANYTHING purely stylistic about the rendering of a particular tag that you shouldn't be able to achieve on any other tag by CSS,
OR
there is, and whatever it is, it is not listed in the style panel when inspecting the element, which means there's something wrong in the Developer Tools.

Does it occur on multiple sites: Yes

Is it a problem with a plugin? No 

Did this work before? No 

Does this work in other browsers? N/A

Chrome version: 55.0.2883.87  Channel: stable
OS Version: 
Flash Version: Shockwave Flash 24.0 r0

Note that there's not even a shadow dom in the legend element, or at least it's not displayed in the developer tools
 

Comment 1 by kojii@chromium.org, Jan 10 2017

Components: -Blink Blink>Forms>Fieldset
Forms are not in the scope of CSS, so you're right that not all effect in forms are doable in CSS. This looks like a by-design to me, but I'd like form experts to chime in.

Comment 2 by teo8...@gmail.com, Jan 10 2017

If it's by design, it's flawed design.

If it's not doable in CSS, then you invent some extended CSS property such as -webkit-whatever that does it, and apply it to the element in the default user-agent stylesheet. 

Comment 3 by tkent@chromium.org, Jan 10 2017

Status: WontFix (was: Unconfirmed)
We don't intend to provide capability to represent everything with CSS, and we don't add vendor-specific CSS properties/values any longer.

Comment 4 by teo8...@gmail.com, Jan 12 2017

Unbelievable. A total shame.
The result of this will be that people will keep using <fieldset> and <legend> when it makes no sense whatsoever semantically, because it's the only way to achieve a given visual effect. Just like people used to do with tables in the nineties.

What you should do is do provide vendor-specific CSS properties/values where the specification is clearly insufficient (if you are visualizing something in a way that is not doable via CSS, then either the specs are insufficient or you shouldn't be doing that), and then fight for the standard bodies to adopt them.

Sign in to add a comment