# Window.confirm without native code?

**URL:** <https://discourse.elm-lang.org/t/window-confirm-without-native-code/844>\
**Category:** Learn\
**Created:** [March 12, 2018, 6:22pm UTC](https://discourse.elm-lang.org/t/window-confirm-without-native-code/844 "2018-03-12T18:22:17Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![xtian](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.elm-lang.org/xtian/32/1178_2.png) [@xtian](https://discourse.elm-lang.org/u/xtian)\
**Post date:** [March 12, 2018, 6:36pm UTC](https://discourse.elm-lang.org/t/window-confirm-without-native-code/844/3 "2018-03-12T18:36:31Z")

</div>

Actually all of the user-hostile behavior that `window.alert` and `window.confirm` used to have has been improved in modern browsers. A StackOverflow post from 2010 is perhaps not the best resource for this information.

For instance: [https://developers.google.com/web/updates/2018/01/nic64#window-alert](https://developers.google.com/web/updates/2018/01/nic64#window-alert)

For simple use-cases, `window.confirm` is a cheap and easy solution that is guaranteed to be accessible and consistent with the browser UI.

So is there a good way to use `window.confirm` with Elm?

---

_[View the full topic](https://discourse.elm-lang.org/t/window-confirm-without-native-code/844)._