You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 10, 2020. It is now read-only.
Based on recent discussion, single expandables should be deprecated and all expandables should appear inside an expandable-group, even if it's one item. o-expandable likely would be deprecated, and o-expandable-group_item or similar added.
Current behavior
Expandables and expandable groups are separate organisms, but are delivered inter-twined.
Expected behavior
Since expandables and expandabled groups are delivered together, they should be fully merged as one organism.
The text was updated successfully, but these errors were encountered:
Expandable.js is turned into a group and no expandable ever appears outside of a group, even if there is only one. Vote 🎉 :
Expandable.js is broken into ExpandableGroup.js and Expandable.js. ExpandableGroup.js handles accordion behavior. Expandable groups and single expandables may both exist. Vote ❤️
Expandable.js has accordion behavior removed and expandable groups disappear. Vote 👍
@cfpb/cfgov-frontends Please vote on one (or if you have a radical 🍣 throw that into the mix and screw up this whole process. Add your vote as an emoji reaction to this comment.
Per chat, going forward I will be pursuing the second option, both ExpandableGroup.js and Expandable.js, and if accordion behavior can be removed, we'll remove ExpandableGroup.js.
Based on recent discussion, single expandables should be deprecated and all expandables should appear inside an expandable-group, even if it's one item.
o-expandable
likely would be deprecated, ando-expandable-group_item
or similar added.Current behavior
Expected behavior
The text was updated successfully, but these errors were encountered: