7 votes2 comments · Microsoft Edge Developer » Document Object Model (DOM) · Flag idea as inappropriate… · Admin →
We’re currently refactoring to add NonElementParentNode and NonDocumentTypeChildNode mixins, as well as move firstElementChild, lastElementChild and childElementCount to the ParentNode mixin.
prepend/append from parentNode are covered by https://wpdev.uservoice.com/forums/257854-microsoft-edge-developer/suggestions/16036408-implement-dom4-methods-prepend-append-befor
qS and qSA should already be supported
The other members are currently only supported on element. I've created a task internally for adding them to the parentNode mixin and hooking them up.
Marking this as in development as not every interface includes the crossOrigin attribute.
...and by anchor, I of course mean `link`. Whoops.
In Edge 15 this is supported as in other browsers, except in anchor elements. See https://developer.microsoft.com/en-us/microsoft-edge/platform/catalog/?page=1&q=crossorigin for details
Previous comment deleted for name calling. Please stay civil.
Service Workers are now under active development in MS Edge. You can track progress at https://developer.microsoft.com/en-us/microsoft-edge/platform/status/serviceworker
@Richard Maher this is not the venue for debating what was discussed in working group face to face or issues with the spec. Please remain on topic.
Thank you for providing a link to background geolocation suggestion. People that support this will vote accordingly. We will take these votes into account when planning what features to work on in the future.
@Richard Maher I don’t have a narrative. This vote is for the specification listed. There are separate voted for Fetch, Push, and so on. I don't see any APIs listed for background geolocation in the link you provided. Like I mentioned previously, if you want to show developer interest and spot for Background Geolocation then create a feedback item and have people vote for it, like they have for other features on this site. Without that we have no way of knowing if they want that feature.
Hi @Richard Maher. This request is for Service Worker. To not dilute the discussion and make it clear what is being voted on, please open a separate feedback item for Background Geolocation. Thanks!
The dialog element is now on the backlog with a priority of medium. You can track status changes at https://dev.modern.ie/platform/status/dialogelementformodals/
CSS Clip Path is currently on the backlog with medium priority. The status can be tracked along with CSS Masking at https://developer.microsoft.com/en-us/microsoft-edge/platform/status/masks/
This is now tracked on our status page at https://dev.modern.ie/platform/status/backdropfilter/
CSS Grid Layout just shipped behind a flag (about:flags → “Enable Unprefixed CSS Grid Layout”) in Windows 10 Insider Preview build 16226.
I've deleted the last comment. Just a reminder to commenters here, ableist language will not be tolerated. Thanks.
Hi @Anonymous. This will not be coming to IE11 as that is in maintenance mode, primarily for enterprise customers who rely on ActiveX and other legacy technology for their internal Line of Business apps.
For many of the most common use cases, such as 2/3 column page layout with header/footer, you can use the old -ms- syntax for IE10 and 11. Generally if you you have a known amount of elements on the page using Grid, then the old syntax will work. Other more complex layouts can be achieved combining Grid with Flexbox children.
Note that this is non-standard (there is no spec) and only works with the really old flex box syntax in WebKit/Blink, not the standard syntax. It also has a number of issues, including not falling back in an elegant way.
Opera supported text-overflow: -o-ellipsis-lastline in Presto, which I personally think was a better solution, but that wasn't accepted for standardisation at the time. The following polyfill includes some information on the pros/cons https://github.com/Merri/ellipsis-lastline
WebM is in development – http://dev.modern.ie/platform/status/webmcontainer/
@John Luther VP9 is in development. Opus is high priority. Vorbis is medium priority. See the following for Opus and Vorbis https://wpdev.uservoice.com/forums/257854-microsoft-edge-developer/suggestions/6513488-ogg-vorbis-and-opus-audio-formats-support-firefox
There are links in that suggestion to the platform status entry for both.
Opus is now in preview builds behind a flag. Please see https://blogs.windows.com/msedgedev/2016/04/18/webm-vp9-and-opus-support-in-microsoft-edge/
@shmeri if you’d like to vote for the OGG container, there is a userVoice suggestions here: https://wpdev.uservoice.com/forums/257854-microsoft-edge-developer/suggestions/9591183-support-ogv-and-ogg-video-and-audio-format-in-micr
@Zeek: WAV is supported in MS Edge.
We’ve just announced that Opus will be supported in IE for ObjectRTC: http://blogs.msdn.com/b/ie/archive/2014/10/27/bringing-interoperable-real-time-communications-to-the-web.aspx
Supporting calc() in flexbox is now on the Microsoft Edge backlog.
As this isn’t part of the spec, I’d recommend checking with the W3C Working Group that is specifying the Gamepad API.
A thread on this topic can be found at http://lists.w3.org/Archives/Public/public-webapps/2014JanMar/0722.html