Steps to reproduce the problem:
1. Open the testcase http://jsbin.com/fiqacod/edit?html,js,output 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 DOM4 methods.
Chrome Bug: https://bugs.chromium.org/p/chromium/issues/detail?id=255482
Firefox Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=911477
Can I Use: http://caniuse.com/#feat=dom-manip-convenience208 votes
These DOM manipulation convenience methods are now on our backlog with a priority of high.
The DOM Standard defines a 'once' option for addEventListener() which causes the callback to only be called once, upon the next occurrence of the given event type, after which the listener gets automatically removed:
The effect is similar to jQuery's popular $.one() method.144 votes
‘once’ shipped in Microsoft Edge included in Windows Insider Preview build 16215.
Edge is now the only browser without support for iterable nodelists. (Chrome, Firefox, Opera, & Safari TP all have it). By iterable nodelists I mean defining `NodeList.prototype[Symbol.iterator]` so that you can spread nodelists like `[...document.body.children]`.
This boils down to implementing something like:
NodeList.prototype[Symbol.iterator] = Array.prototype[Symbol.iterator];123 votes
Iterables on DOM objects are now in development in Microsoft Edge.
Provide full support of the accept attribute in a input type="file"
Allows you to restrict the UX to valid file formats when necessary. Image uploads, PDF's, etc.110 votes
In Edge WebDriver, the get element text always show extra whitespace characters as prefix and/ or suffix. Probably it returns an element's text as rendered using innerText. This is not in line with other webdrivers like Chrome, Safari and "Microsoft" IE webdriver.
Will be good if you can fix it to trim the extra whitespace characters by default. Will be very helpful, Thanks!32 votes
Currently on Edge (also on IE), trying to fetch a data-URL like "data:text/plain;charset=ISO...,...text..." fails - as it is considered cross-domain.
All other major browsers allow this.
This is useful for converting "exotic" charsets.21 votes
Firefox (since ages) and Chrome (since 08/2016) search datalist items using "contains". However, IE still uses "starts with" to filter datalist items.
It can easely be tested here:
I think IE should adopt a "contains" approach too to filter items, as it is by far more useful/practical ...and would behave similarly to FF/chrome.11 votes
Edge only supports msToBlob() currently. Please support standard toBlob().11 votes
Browser extensions such as Stylus/Stylish use templates which call .firstElementChild but we can't port these to Edge because the full DocumentFragment api isn't supported right now.7 votes
All other things being equal, EdgeHtml (13.10586) seems to be about 5 times slower than IE11 (11.0.32) for simple XPath queries like a[position()=3]/b[position()=3]5 votes
Standard specification at https://html.spec.whatwg.org/multipage/interaction.html#dom-accesskeylabel
Already implemented in Mozilla Firefox.
Implementing this in Microsoft Edge would improve performance for websites using this (such as Wikipedia) by not having to load a polyfill that infers this information based on heuristics such as User-Agent strings and OS information.
This is a simple property accessed through the DOM that returns a string representing the keyboard combination used for access keys. This varies from browser to browser and between different operating systems and devices (mostly desktop however).5 votes
In order to feature detect resource hinting rels like prefetch, preload, and dns-prefetch, please implement relList and relList.supports as added to the dom spec in https://github.com/whatwg/dom/pull/123 . relList.supports is implemented in current Firefox and Chrome browsers. It is not yet implemented in Safari, but the resource hinting is also not implemented, so feature testing for that is a true negative. However, Edge supports resource hinting, but feature testing is a false negative, which means developers have to resort to User Agent inference or forgo resource hinting, resulting in a slower experience for users.4 votes
DOM functions currently return 0 when queried for length. While browsers implement the number of required parameters differently due to differences in their optional parameters and values, it would help determine differences between browsers if we could compare functions required parameter counts across browsers.3 votes
This is now in development \o/
Returns the closest element which controls the position of current element with a scroll.
This feature very useful in many cases, easy for browsers to implement and hard for plugins such as jQueryUI to get it right.
IE is the only browser that doesn't allow a element created on one window to be added to another. This is useful when creating popout windows in a web application and not all frameworks allow you to specify the document with which to create the element with.3 votes
It would be nice to have the ability to control whether Edge tries to select entire words within a specific context. Perhaps using some (custom) CSS rule.3 votes
- Don't see your idea?