Kevin Ansfield 4c5144cb61 🐛 Fixed close button on "unsaved changes" modal not always behaving like "Stay" button ... no issue The close button in the unsaved changes modal used the `@close` action directly compared to the "Stay" button which used `(fn @close false)`. The close button version without explicit arguments resulted in the first argument being a `PointerEvent` instance which if checked as a modal return value as `if (shouldClose)` would evaluate as truthy therefore matching the "Leave" behaviour instead of the "Stay" behaviour. - changed modal to explicitly call `(fn @close false)` when the close button is clicked - updated design settings route to have an explicit `shouldLeave === true` check so default behaviour is always "Stay"		2022-04-14 12:39:10 +01:00
..
change-theme	Resolved deprecation warnings for dynamic modal component binding (#2303)	2022-03-14 10:52:04 +00:00
change-theme.js	Refactored away CurrentUserSettings mixin (#2200)	2022-01-17 10:05:27 +00:00
index.js	🐛 Fixed close button on "unsaved changes" modal not always behaving like "Stay" button	2022-04-14 12:39:10 +01:00