Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Docs: carousel, collapse, navs (tabs), popovers should use buttons rather than faked link buttons
See original GitHub issueThere’s no good reason (other than ease of styling) for https://v5.getbootstrap.com/docs/5.0/components/carousel/, https://v5.getbootstrap.com/docs/5.0/components/collapse/, https://v5.getbootstrap.com/docs/5.0/components/navs/#javascript-behavior, https://v5.getbootstrap.com/docs/5.0/components/popovers/#dismiss-on-next-click to use <a href="#..." role="button">...</a> pseudo-buttons. While sure, BS can still support this, it’d be good to lead by example and use the correct <button> element for this (though I don’t believe we have a neutral-enough button style out of the box to support carousel buttons…or at least, the current carousel controls need to be extended to neutralise the remaining button styles that creep in when swapping out the elements).
Issue Analytics
- State:
- Created 3 years ago
- Reactions:2
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Closing this as - apart from popovers using links, which is still necessary with our current approach due to Safari/macOS’s odd duck behaviour, copied by Firefox/macOS - all major things are now sorted.
We don’t assign issues to people and there’s no need to ask for permission 😃 Just grab an issue, work on it and make a PR when ready.