Decide on the future of the collapsing list component

[adamzap]

Before I refactor the JavaScript for the collapsing list component, I want to make sure we that we still want to use it on the site.

This component gives animated collapsing functionality to lists and adds "Expand All" and "Collapse All" buttons.

The collapsing list component is used in four places:

1. The "Intro to Django" section of Getting Started with Django
   • A standard use of the component
2. The "Django RSS Feeds" section of Community
   • A standard use of the component
3. The "Archives" section of the the blog sidebar
   • Customized to hide the "Expand All" and "Collapse All" buttons
4. The bottom of the Style Guide
   • This use doesn't count

So it's used, but not much.

I think these are our options:

1. Keep the component as-is and refactor the JavaScript
2. Replace it with simpler, more specific JavaScript
   • Remove the animation?
   • Remove the "Collapse All" button?
   • Etc.
3. Remove the JavaScript altogether and use the details element
   • This would probably require a bit of CSS

I'm curious what other WG members think. I will be happy to to implement any of the above or another idea.

[pauloxnet]

I prefer using details since it doesn't require any custom JavaScript for a feature already available in the browser.

IMO generally speaking every feature that we can implement directly with HTML, or CSS it's better than using JavaScript.

That said I think also that in some cases like blog feeds using an accordion to show/hide it's not the best option from UX point of view.

[SaptakS]

I agree with @pauloxnet . I would go with replacing it with details-summary and updating the CSS to make it look similar. The expand-all, collapse-all would probably still need Javascript, which is fine.

[jcjudkins]

I agree HTML and CSS over JavaScript. Also, a fan of JavaScript if it makes it less of a headache.