Feature proposal #6912
closed
- Subject changed from Upgrade fontawesome to 5 to Upgrade to fontawesome 5
Use a second CSS class to migrate fontawesome 4 usages to fontawesome 5. Add parameter to disable it as well just like jQuery migration. Once all of core usages have been migrated this can be changed to default disabled and eventually removed.
https://fontawesome.com/how-to-use/upgrading-from-4
Example migration for alternative styling to new naming convention:
.cb_template .fa[class*="-o"]
should be attached to .cb_template .far
, which ensures the correct font will be used for those styles. Others will just need flat out to duplicate some code, but can all be generated using SCSS.
- Target version changed from CB 2.2 to CB 2.8
- Target version changed from CB 2.8 to CB 2.4.3
- Target version changed from CB 2.4.3 to CB 2.4.4
- Target version changed from CB 2.4.4 to CB 2.4.5
- Target version changed from CB 2.4.5 to CB 2.4.6
- Target version changed from CB 2.4.6 to CB 2.4.7
- Target version changed from CB 2.4.7 to CB 2.5.0
- Target version changed from CB 2.5.0 to CB 2.6
- Target version changed from CB 2.6 to CB 2.6.1
- Target version changed from CB 2.6.1 to CB 2.7
- Target version changed from CB 2.7 to CB 2.7.2
- Target version changed from CB 2.7.2 to CB 2.7.3
- Target version changed from CB 2.7.3 to CB 2.7.4
- Target version changed from CB 2.7.4 to CB 2.8
- Target version changed from CB 2.8 to CB 2.8.1
- Target version changed from CB 2.8.1 to CB 2.8.2
- Target version changed from CB 2.8.2 to CB 2.9.0
- Target version changed from CB 2.9.0 to CB 2.9.2
- Target version changed from CB 2.9.2 to CB 2.9.3
- Target version changed from CB 2.9.3 to CB 2.10.0
- Subject changed from Upgrade to fontawesome 5 to Upgrade to fontawesome 6
- Status changed from Assigned to Resolved
- % Done changed from 0 to 100
Handled by FontAwesome v6 Compatibility Mode.
- Status changed from Resolved to Closed
Also available in: Atom
PDF