Project

General

Profile

Actions

Feature proposal #6912

closed

Upgrade to fontawesome 6

Feature proposal #6912: Upgrade to fontawesome 6

Added by krileon about 8 years ago. Updated 12 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Start date:
08 December 2017
Due date:
% Done:

100%

Estimated time:

Description

Fontawesome 5 has been released, but it changes the "fa" class prefix to the following multiple prefixes.

Solid: fas
Regular: far
Brands: fab

All usages would need to be updated mainly where -o icons were being used.

https://fontawesome.com/how-to-use/svg-with-js#styles-and-prefixes

Updated by krileon about 8 years ago Actions #1

  • Subject changed from Upgrade fontawesome to 5 to Upgrade to fontawesome 5

Updated by krileon about 8 years ago Actions #2

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.

Updated by krileon over 7 years ago Actions #3

  • Target version changed from CB 2.2 to CB 2.8

Updated by krileon over 6 years ago Actions #4

  • Target version changed from CB 2.8 to CB 2.4.3

A CSS shim is now provided.

https://fontawesome.com/how-to-use/on-the-web/setup/upgrading-from-version-4#shims

This should make upgrading much easier as we will need to use the shim until all usages can be upgraded. The shim should completely resolve migration issues so shouldn't be any B/C concerns. Needs testing.

Updated by beat about 6 years ago Actions #5

  • Target version changed from CB 2.4.3 to CB 2.4.4

Updated by beat almost 6 years ago Actions #6

  • Target version changed from CB 2.4.4 to CB 2.4.5

Updated by beat over 5 years ago Actions #7

  • Target version changed from CB 2.4.5 to CB 2.4.6

Updated by beat over 5 years ago Actions #8

  • Target version changed from CB 2.4.6 to CB 2.4.7

Updated by beat about 5 years ago Actions #9

  • Target version changed from CB 2.4.7 to CB 2.5.0

Updated by beat almost 5 years ago Actions #10

  • Target version changed from CB 2.5.0 to CB 2.6

Updated by beat over 4 years ago Actions #11

  • Target version changed from CB 2.6 to CB 2.6.1

Updated by beat over 4 years ago Actions #12

  • Target version changed from CB 2.6.1 to CB 2.7

Updated by beat almost 4 years ago Actions #13

  • Target version changed from CB 2.7 to CB 2.7.2

Updated by beat almost 4 years ago Actions #14

  • Target version changed from CB 2.7.2 to CB 2.7.3

Updated by beat over 3 years ago Actions #15

  • Target version changed from CB 2.7.3 to CB 2.7.4

Updated by krileon over 3 years ago Actions #16

  • Target version changed from CB 2.7.4 to CB 2.8

Updated by beat almost 3 years ago Actions #17

  • Target version changed from CB 2.8 to CB 2.8.1

Updated by beat over 2 years ago Actions #18

  • Target version changed from CB 2.8.1 to CB 2.8.2

Updated by beat over 2 years ago Actions #19

  • Target version changed from CB 2.8.2 to CB 2.9.0

Updated by beat about 2 years ago Actions #20

  • Target version changed from CB 2.9.0 to CB 2.9.2

Updated by beat over 1 year ago Actions #21

  • Target version changed from CB 2.9.2 to CB 2.9.3

Updated by beat over 1 year ago Actions #22

  • Target version changed from CB 2.9.3 to CB 2.10.0

Updated by krileon 12 months ago Actions #23

  • 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.

Updated by beat 12 months ago Actions #24

  • Status changed from Resolved to Closed
Actions

Also available in: PDF Atom