ng-open doesn't work on Mozila Firefox 28.0+

[fals]

There's some bug related to ng-open and Mozila Firefox 28.0+. Even the live demo from Angular JS doesn't work as expected.

[caitp]

This is kind of not implemented in gecko just yet, see https://bugzilla.mozilla.org/show_bug.cgi?id=591737

We aren't polyfilling html5 elements here, we're just allowing you to control them via model values.

[caitp]

However, it looks like there are some polyfill'd implementations that you might be able to use: https://github.com/Modernizr/Modernizr/wiki/HTML5-Cross-Browser-Polyfills#details-and-summary (I don't know how compatible these are with ng-open, though).

cc @petebacondarwin / @matsko if the docs app is broken in FF/IE, it might be worth temporarily leveraging some of these polyfills. But it doesn't really hurt the site since the summary isn't hidden from users

[petebacondarwin]

The more I look at it the less I like the <details> element in HTML5. It has limited support in browsers, yes but this is only the tip of the iceberg.

The real nastiness comes from the fact that when the details are closed it does not change any styles on the contents, which should now be hidden. What I mean is that if you have a <p> inside the details, it is not possible, by looking at the <p> to tell whether it is visible or not. Correct me if I'm wrong.

Moreover, I tend to agree with a commenter on HTML5 doctor, that this seems an unnecessary additional markup when <article> and <h1> with a splash of JavaScript could serve the same purpose and with more versatility than <details>.

I suggest that rather than hack around with the demo trying to get it to appear to work on non-compliant browsers, we should just put in a big disclaimer and point people at ng-show/ng-hide instead.

[Narretz]

We added a note to the docs.