Releases: GoogleChrome/dialog-polyfill
Releases · GoogleChrome/dialog-polyfill
January 2017
- Moves to
MutationObserver
and improves catching dialog removals (while continuing to support mutation events for IE10 and below) - Detects invalid placements of modal dialogs (within a stacking context), warning the user with
console.warn
, and tries to allow use anyway - Downgrades dialogs that are moved within a page (modal => normal), matching Chrome
- Fixes an issue where focus was performed before a dialog was shown
- Fixes an issue where inner non-modal dialogs were unfocusable
November 2016
- Removes leftover debug messages and additional listener.
July 2016
February 2016
September 2015
Fixes minor issues-
- Supports forms inside dialogs without
method
activeElement
element blur sanity-check for IE- Fix center alignment if dialog is taller than viewport
September 2015
This is a tiny update just to match NPM's published 0.4.1 version.
August 2015
Since the last release, some highlights-
- Test suites
- The
open
attribute and other state calls use the same backing valueopen
is observed by the browser
- Better support for
<form method="dialog">
and settingreturnValue
- More stable class-based rewrite
- Limit to number of open modal dialogs
- Simplified focus blocking
- Other minor updates to match the W3C spec
- Default CSS updates for small-screen browsers
Additionally, note that dialogPolyfill.registerDialog
is now a noop on browsers with dialog support, such as Chrome. If you'd like to force use of the polyfill (with unpredictable results), please call dialogPolyfill.forceRegisterDialog
.
There are still some unresolved issues in IE9/10. We'd appreciate user feedback.
February 2015
Merge pull request #41 from samthor/tag-3 0.3.0 release