Finalise (and Release) Bootstrap 4 Support
See original GitHub issueAs of 10 Aug 2017 Bootstrap 4 has moved from “Alpha” to “Beta”.
This should bring the stability we’ve been missing:
Long story short, shipping a beta means we’re done breaking all your stuff until our next major version (v5). We’re not perfect, but we’ll be doing our best to keep all the classes, features, and docs URLs as they appear now in this release. — Announcement Blog Post
I’m not using Bootstrap myself currently — so I need help with this!
I’m going to close all other bootstrap 4 issues and will take PRs Ref #732
helping to bring the Bootstrap 4 support up to scratch.
I’m planning a new release of Crispy Forms in the Autumn — before Django 2.0. If we get good input here I will bring that forward.
Thanks for the input everyone!
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:19 (10 by maintainers)
Top Results From Across the Web
Introducing our Long Term Support plan - Bootstrap Blog
As part of this initiative, each major version of Bootstrap will receive at least six months of support after it is retired, followed...
Read more >Introduction - Bootstrap
Get started with Bootstrap, the world's most popular framework for building responsive, mobile-first sites, with jsDelivr and a template starter page.
Read more >Migrating to v4 - Bootstrap
Rewrote component with flexbox. Given move to flexbox, alignment of dismiss icons in the header is likely broken as we're no longer using...
Read more >Bootstrap v4.6.2
Follow our release repo to stay in the loop on release maintenance status. Support the team. Visit our Open Collective page or our...
Read more >Versions · Bootstrap v5.2
An appendix of hosted documentation for nearly every release of Bootstrap, from v1 through v5.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Currently errors don’t appear to be working with bs4 beta 2 (or beta) but they do work with alpha 6. (posting this here rather than a separate issue, but let me know if you would prefer separate).
This example form: https://gist.github.com/yunti/8c091cd446082eb1208e076594fc2439
Generates this output, which uses bs4 beta 2 and shows missing error: https://codepen.io/anon/pen/GOOdmM
Same output but with bs4 alpha 6 which has error displayed: https://codepen.io/anon/pen/JOOvyG
update: its a bs4 bug https://github.com/twbs/bootstrap/issues/23454
@zoidbergwill:
First, no stress! OSS is a labour of love and often other things take priority. Anyone who doesn’t understand that needs to reassess. ❤️
Second: Great! It’s time for a new version of CF and if we can get BS4 compat finalised (bar the inevitable edge-cases) that would be a great addition.