Currently dialogPolyfill.forceRegisterDialog(element) throws a console.warn when the native <dialog> is supported, which is making the debugging of other error output difficult within our codebase. Shouldn't the polyfill transparently leave native support up to the browser in these cases? See
|
dialogPolyfill.forceRegisterDialog = function(element) { |
Currently dialogPolyfill.forceRegisterDialog(element) throws a
console.warnwhen the native<dialog>is supported, which is making the debugging of other error output difficult within our codebase. Shouldn't the polyfill transparently leave native support up to the browser in these cases? Seedialog-polyfill/dist/dialog-polyfill.js
Line 536 in 5033aac