Open Watso196 opened 1 year ago
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 https://github.com/GoogleChrome/dialog-polyfill/blob/5033aac1b74c44f36cde47be3d11f4756f3f8fda/dist/dialog-polyfill.js#L536
console.warn
<dialog>
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? See https://github.com/GoogleChrome/dialog-polyfill/blob/5033aac1b74c44f36cde47be3d11f4756f3f8fda/dist/dialog-polyfill.js#L536