ryanflorence/chrome-dialog-element.md

Last active December 24, 2015 14:39

Star (1) You must be signed in to star a gist
Fork (0) You must be signed in to fork a gist

Learn more about clone URLs
Clone this repository at <script src="https://gist.github.com/ryanflorence/6814517.js"></script>
Save ryanflorence/6814517 to your computer and use it in GitHub Desktop.

Download ZIP

Raw

chrome-dialog-element.md

Context: http://updates.html5rocks.com/2013/09/dialog-element-Modals-made-easy

show and close are not opposites. It should be open, close or show, hide. open close is the obvious winner.
There is no declarative api, which is actually really simple:

<button controls="my-dialog">
  Toggle Dialog
</button>

<dialog id="my-dialog" open>
  Hello
  <button controls="my-dialog">close</button>
</dialog>

Using controls to mimic WAI ARIA aria-controls attribute. Could also use for.

OliverJAsh commented Oct 3, 2013

+1!

Have you lurked on the various mailing lists (WHATWG) to see what the deal is here?

mfalken commented Oct 7, 2013

The <dialog> implementation in Chrome tries to follow the spec.

The show/close naming is being discussed on the WHATWG mailing list, with the main thread at the end of:
http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2013-September/040897.html
So far, the names remain as they are.

As pointed out on IRC and Twitter, <form method="dialog"> exists in the spec (but it's not yet implemented in Chrome). But there is no declarative way for an open button.

Providing feedback to the WHATWG mailing list or other channels can be a good way to influence changes to the spec.