#type details: Remove #collapsible property

@sun Could we also please only make the first summary/details on a page #open TRUE, and the successive ones #open FALSE? Opening them all kind of defeats the purpose right?

#1886728: Switch from details to fieldset when collapsing isn't needed is an example of something that should be a fieldset again

Yes, #6 makes sense.

@sun I see. I thought that summary and details was an effort to make us more semantic and replace fieldsets. What are the criteria for when summary and details are appropriate vs fieldsets?

@Sun Just looked at #1886728 which spurred me to think this through more deeply. Seems to me that the purpose of summary and details is to provide a semantic underpinning for things that expand to reveal more information. If that is the case then logic dictates we should be S&D everywhere in place of collapsible fieldsets (collapsible being the key word; styled divs that do not collapse would be fine).

Then the only remaining question is "what are the criteria for determining when detatils open='true' vs.'false' "? so we can implement that in core and add to HIG.

Great!

swenteldoos-2:drupal swentel$ git apply type.details.11.patch 
swenteldoos-2:drupal swentel$ rm type.details.11.patch 
swenteldoos-2:drupal swentel$ grep -R '#collapsible' *
swenteldoos-2:drupal swentel$

Should be fine when it comes back.

need reroll because of #1886728: Switch from details to fieldset when collapsing isn't needed Leaving RTBC, there is one #collapsible remove less from simpletest.pages.inc

reroll

Nitpicking here but a couple of the docblocks could be re-wrapped, they wrap early. Interdiff is against #16.

#18: 1852104-18.patch queued for re-testing.

Back to RTBC. I reviewed the patch as well and agree with RTBC.

Re-rolled to fix merge conflict in NodeFormController.

Alright, committed to 8.x. Thanks!