Ryan McGeary

@Svyatov Unless you really are skipping a lot of core bootstrap styles to make the resulting stylesheet smaller, that solution seems like a [DRY](http://en.wikipedia.org/wiki/Don't_repeat_yourself) violation. I think the best solution...

Is this still an issue worth keeping open? If not, does the latest v3.0.0.1 release fix your issue and/or does #25 help?

I think font-awesome-sass-rails should just remain as a light wrapper around Font-Awesome core. If you'd like an icon mixin, I think that should only be addressed in the FortAwesome/Font-Awesome repo....

@AJ-Acevedo Try the [font-awesome-rails](https://github.com/bokmann/font-awesome-rails) gem. It works with Rails 3.2 and Rails 4 (assuming sass-rails master). If you need Rails 3.1, there's a locked version specific for that too. It...

> I'm not sure why the backtrace says "ruby/2.5.0" instead of 2.5.3 FYI: That's just how ruby and rubygems and hence bundler manages the directory path for gems. Ruby 2.5.1,...

It looks like the more recent pull-requests that came in for this gem all broke the build. I wouldn't blame @thetron for ignoring those. As an attempt at rejuvenating this...

@kenneth1870 I'm not a huge fan of forking open source projects for reasons such as this unless all other options are exhausted, but I understand your frustration. However, in the...

@daniloakamine I haven't touched the project that relied on this particular pull-request in a while now, but I'll probably be near that codebase in the next couple weeks or so....

I just tried the demo page with jQuery 2.2.2. Up and down keys worked as expected.

@virgofx Oh. I see. The keyboard navigation doesn't jump past disabled entries. Reopening this issue.