Incorrect CSS3 text-decoration Implementation

By design Issue #13391907

Details

Author
Dexter L.
Created
Aug 23, 2017
Privacy
This issue is public.
Found in
  • Microsoft Edge
Found in build #
15.15063
Reports
Reported by 3 people

Sign in to watch or report this issue.

Steps to reproduce

text-decoration value cannot allow shorthand syntax with text-decoration-style and text-decoration-color included.
Also, the standalone properties text-decoration-line, text-decoration-style and text-decoration-color are not supported.

Example: HTML:

<div id="text1">Text 1 Result</div>
<div id="text2">Text 2 Result</div>

CSS:

#text1 { text-decoration: underline wavy;}
#text2 { text-decoration-line: underline; text-decoration-style: double; text-decoration-color: red;}

Attachments

Comments and activity

  • Microsoft Edge Team

    Changed Assigned To to “James M.”

    Changed Status to “By design”

  • Edge currently does not support CSS 3 Text Decorations (only the spec as it was defined in CSS 2.1) so the behavior you are seeing is expected. We are constantly looking for ways to improve our product and have implementing further refinements of the spec on our backlog, though we don’t have any specifc plan to share as of right now. Feel free however to use our uservoice website and upvote/create a feature request. We only use this website to keep track of bugs, not feature requests.

  • Can I just ask one important question?

    why?

  • This is a pretty core and basic spec of CSS3, I don’t think this is a feature but a standard that a browser should follow.

  • Changed Status from “By design”

  • So, this should be an issue but not a “new” feature to be delivered, where I expect “features” are those specs that are still in draft or newly recommended in recent months.

  • Microsoft Edge Team

    Changed Status to “By design”

  • By new feature we mean adding support for any css property not supported in Edge today. Adding support for a new property is not a bug fix, and takes considerably more effort.

    It’s not that we don’t want to add support for these properties, but keeping feature request in our bug database isn’t helping anyone. These bugs clutters our searches, and are not actionable because we are not allowed to “fix” the bug except manually like I am doing now which we will most likely forget to do when we will actually implement the feature (we cannot commit new features by referencing a bug, we need to reference deliverables and keep track of time being spent differently, which bugs do not allow to do).

    Please use the uservoice, really.

  • Francois, thanks for your explanation. 😁
    Sorry for misunderstanding some bug definitions.
    Hope you can focus on fixing other bugs quickly, and implement uservoice ideas as soon as possible to transform Edge as the best browser. 💪🏼

You need to sign in to your Microsoft account to add a comment.

Sign in