Description
Make the carousel docs page more sensible/logically structured:
- start with static/non-autoplaying examples
- explicitly mention that carousels currently need to be manually initialized
- split out and explain autoplaying
data-bs-ride="carousel"and the weird "autoplay after first interaction"data-bs-ride="true"behaviour, as well as the fact that when animating, these carousels pause on hover/focus - various minor language/wording tweaks
In addition, this now explicitly initialises all carousels, so their touch behaviour will work right after page load (rather than only after the first click on a prev/next button).
Type of changes
-
Bug fix (non-breaking change which fixes an issue) -
New feature (non-breaking change which adds functionality) -
Refactoring (non-breaking change) -
Breaking change (fix or feature that would change existing functionality)
Checklist
-
I have read the contributing guidelines -
My code follows the code style of the project (using npm run lint) -
My change introduces changes to the documentation -
I have updated the documentation accordingly -
I have added tests to cover my changes -
All new and existing tests passed