Microsoft Edge Developer
Hi, are you a web developer or designer?
“No, I just want to share feedback on Microsoft Edge.”
Please use the Feedback Hub (requires Windows 10) to submit your feedback in the Microsoft Edge category. This site is for web developer and designer feedback only. Other feedback will be closed without action.
“Yes, I’m a web developer or designer with feedback for the Microsoft Edge platform.”
Great! This site is where the Microsoft Edge team collects feature requests from the web developer and designer community in the categories listed to the right. For bugs on existing features, please log an issue on the Issue Tracker.
Your feedback will help us with planning and to better understand how web developers and designers are using the platform. Top standards-based feature requests will also be copied over to status.microsoftedge.com, where you can track its development status.
For the most actionable feedback, please search and up vote for existing suggestions before submitting a new suggestion, and create a separate suggestion per idea. Note that off topic or inappropriate suggestions may be moderated. The Microsoft Edge team will use suggestions as an important input, but there are several additional factors that inform the final roadmap.
A note from our lawyers: Please do not send any novel or patentable ideas, copyrighted materials, samples or demos which you do not want to grant a license to Microsoft. See the Terms of Service for more information.
-
21 votes
-
Suport for calc in rotate/scale/for time vals
But there's still something missing & with vars now supported, it's more important than ever: calc in rotate/scale/for time vals.
43 votes -
3 votes
-
54 votes
-
stop support of 'ime-mode' with recommendation of W3C
At least, Edge should offer the option which ignores 'ime-mode'.
FYI:
CSS Basic User Interface Module Level 3 (CSS3 UI)
W3C Candidate Recommendation, 02 March 2017
https://www.w3.org/TR/css-ui-3/#input-method-editor
> 6.3.2. Obsolete: the ime-mode property
> User agents should not support the ime-mode property.12 votes -
#rrggbbaa and #rgba color notation support
Couldn't find this anywhere here, so I'll post this feature request.
I'm asking for support of the following notations:
background-color: #12345678;
and
background-color: #1234;
172 votes -
Implement caret-color support
"caret-color" has just been implemented on Chromium and Firefox. It'd be really nice if Edge can support it too.
The spec is CR: https://www.w3.org/TR/css-ui-3/#caret-color
And there are already 21 tests on the W3C csswg-test repo: http://test.csswg.org/shepherd/search/testcase/spec/css-ui-3/section/6.2.1/
68 votes -
Case-insensitive attribute selector (i flag)
The `i` flag is defined in the CSS Selectors module [1] and is supported by all the other major browser engines.
45 votes -
Implement sideways-rl and sideways-lr values for CSS Writing Modes.
The Writing Mode property has been implemented and updated in the current version of Edge, but it only includes the values of horizontal-tb, vertical-lr and vertical-rl. Two more values provide an easier way for authors to typeset text in a sideways orientation. They are currently implemented in Firefox (since Sept 2015).
https://www.w3.org/TR/css-writing-modes-3/#valdef-writing-mode-sideways-rl
36 votes -
Support pseudo elements in <input>
This feature would add support for ::before and ::after pseudo elements in <input> elements. Chrome, Opera, and Safari already support using pseudo elements to embellish inputs without the need for JavaScript and extra divs.
71 votes -
Transform bug with scrollbars
When I move a div out of its parent using absolute positioning, and move it back into parent using transform, the scrollbars are still there, resulting in a blank scroll area! (the parent is overflow:auto or scroll) According to the w3c's specification, the scrollbars should disapear which just happens in chrome and firefox.
The specification is as follows:
For elements whose layout is governed by the CSS box model, the transform property does not affect the flow of the content surrounding the transformed element. However, the extent of the overflow area takes into account transformed elements. This behavior is similar…6 votes -
Implement nth-child(An+B of sel) and nth-last-child(An+B of sel) pseudo classes
Steps to reproduce the problem:
1. Open the testcase https://bugzilla.mozilla.org/attachment.cgi?id=8443862 in Edge.What is the expected behavior?
The test should pass.What went wrong?
The test failed, indicating that Edge does not support the relevant nth-child(An+B of sel) and nth-last-child(An+B of sel) pseudo classes.Specification: https://drafts.csswg.org/selectors-4/#the-nth-child-pseudo
Chrome Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=304163
Firefox Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=854148
Webkit Status: https://webkit.org/status/#feature-css-selector-:nth-child(an+b-of-selector-list)-and-:nth-last-child(an+b-of-selector-list)
Can I Use: http://caniuse.com/#feat=css-nth-child-of60 votes -
image-orientation
Add support for image-orientation:from-image. This will allow photos captured on Windows 10 Mobile devices to be displayed with the correct orientation.
To demonstrate the issue, see: https://social.msdn.microsoft.com/Forums/Windowsapps/en-US/78294ed7-7258-4ef2-b90c-2de237f93ba1/uwpxamlhmtl-webview-displaying-captured-photos-with-incorrect-orientation-on-windows-10-mobile?forum=wpdevelop
20 votes -
@scope
Scoped Styles via @scope
@scope at-rule to apply a block of rules only within a subtree of the document. The cascade would prioritize scoped rules above unscoped ones, regardless of specificity.
https://drafts.csswg.org/css-scoping/
(This is similar to scoped styles in this post: https://wpdev.uservoice.com/forums/257854-microsoft-edge-developer/suggestions/6508310-scoped-styles -- but the newer revision of the draft uses an at-rule rather than the HTML `scoped` attribute)
194 votes -
Ability to style select options.
Ability to style select options. e.g. I'd like to layout options horizontally instead of vertically (e.g. toggle button style for Yes/No, Male/Female, etc.).
8 votes -
Implement text-fill/text-stroke
See
- http://caniuse.com/#feat=text-stroke
- https://css-tricks.com/adding-stroke-to-web-text/- https://developer.mozilla.org/en-US/docs/Web/CSS/-webkit-text-fill-color
- https://developer.mozilla.org/en-US/docs/Web/CSS/-webkit-text-stroke-color
- https://developer.mozilla.org/en-US/docs/Web/CSS/-webkit-text-stroke-width
- https://developer.mozilla.org/en-US/docs/Web/CSS/-webkit-text-strokeComing from https://github.com/Fyrd/caniuse/issues/2823
22 votes -
vector-effect
Support vector-effect for SVG elements. vector-effect: non-scaling-stroke would allow strokes to keep the same width as the SVG scales as a whole. https://www.w3.org/TR/SVGTiny12/painting.html#VectorEffectProperty
75 votes -
:placeholder-shown CSS pseudo-class
Implement the :placeholder-shown CSS pseudo-class
- http://caniuse.com/#feat=css-placeholder-shown
- https://drafts.csswg.org/selectors-4/#placeholder671 votes -
Automatic links (like for detected phone numbers) need to be stylable
Currently the links Edge creates for automatically detected phone numbers cannot be styled as far as I know. This means they look bad and out-of-place in websites, and many site owners would opt to disabling the feature on their site altogether which would hurt users.
I guess that this issue exists due to the fact that Edge doesn't change the DOM when creating these links, so they aren't matched by CSS "a" selectors (which works on iOS, as far as I know). I see two possible solutions:
a) Infer link styles from the containing element, so the automatic links look…
17 votes -
Implement :focus-within from Selectors 4
Tons of UIs include elements that are not visible unless the user interacts with their parent or ancestor. Think popup menus, delete or edit buttons, floating formatting toolbars, copy buttons, editing popups and so on. The list is endless. This is a good way to reduce visual clutter.
However, this is often done in an inaccessible way, just by using :hover, because making it accessible requires JS, since :focus does not apply to ancestors. However, 1 in 2 people writing HTML/CSS are not comfortable with JavaScript so keyboard accessibility (and usability, as many of us are keyboard users by choice)…746 votes
- Don't see your idea?