The main barrier to legacy support is FontAwesome's use of the pseudo `:before` element for specifying the unicode icon value in the `content` attribute. I think it might be possible to support browsers such as IE9 and IE10, if we allow the icon to be specified as the FontAwesome unicode value instead the string name. Obviously this is not ideal, as instead of a nice, human readable name, you'd be looking at unicode: - `.awesomeCursor('pencil');` vs. `.awesomeCursor('\uf040');` The pages for individual icons on the [FontAwesome site](http://fontawesome.io/icons/) do list the unicode values, which is a plus.
AI Analysis
This issue appears to be discussing a feature request or bug report related to the repository. Based on the content, it seems to be still under discussion. The issue was opened by jwarby and has received 0 comments.
Add a comment
Comment form would go here