RESOLVED DUPLICATE of bug 169009116922
Remove text-line-through, text-overline, and text-underline
https://bugs.webkit.org/show_bug.cgi?id=116922
Summary Remove text-line-through, text-overline, and text-underline
Ryosuke Niwa
Reported 2013-05-29 00:25:23 PDT
Consider merging https://chromium.googlesource.com/chromium/blink/+/31b2e8ac46fac72374b04385c44d0e3eec9d4d3e Drop 3 properties that were never parsed These properties would always return false during parsing, which means that they would be recognized but an author would never be able to set them. The only documentation about them is that they belong to the list of CSS 3 unimplemented features in Blink / WebKit but none of the CSS 3 specifications reference them. CSS 3 Text Decoration will introduce equivalent fonctionalities in a standard way.
Attachments
Sam Weinig
Comment 1 2013-05-29 14:58:04 PDT
I kind of like these features. I think we should consider implementing them even if the specs don't currently support them.
Bruno Abinader (history only)
Comment 2 2013-06-03 06:35:44 PDT
(In reply to comment #1) > I kind of like these features. I think we should consider implementing them even if the specs don't currently support them. From implementation point of view, it would be as easy as aliasing each property to the respective CSS3 Text Decoration implementation.
Ahmad Saleem
Comment 3 2022-09-28 04:57:30 PDT
Do we need to anything here? Considering these are in CSS3 Text Decorations. Thanks!
Karl Dubost
Comment 4 2025-10-23 00:01:35 PDT
The specification for CSS3 Text decorations defines text-underline-position https://drafts.csswg.org/css-text-decor/#text-underline-position-property text-decoration-line https://drafts.csswg.org/css-text-decor/#text-decoration-line-property with the values none | [ underline || overline || line-through || blink ] But indeed the old values seem to be still implemented it seems. https://wpt.fyi/results/css/css-conditional/js/CSS-supports-CSSStyleDeclaration.html
Tim Nguyen (:ntim)
Comment 5 2025-10-26 08:22:58 PDT
*** This bug has been marked as a duplicate of bug 169009 ***
Note You need to log in before you can comment on or make changes to this bug.