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 do list the unicode values, which is a plus.
The main barrier to legacy support is FontAwesome's use of the pseudo
:beforeelement for specifying the unicode icon value in thecontentattribute.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 do list the unicode values, which is a plus.