News for hackers. Stuff that matters.
Re:Font Awesome 4.1 released by colinramsay on Saturday May 17, 2014 @10:15AM (#7760170)
That's about five or six people affected by that problem then...
Re:Font Awesome 4.1 released by Yetanfou on Saturday May 17, 2014 @11:29AM (#7760393)
You might be surprised there. The fonts don't show up for those who use NoScript in default-deny mode (which is the suggested, and default, mode for this popular extension) either. Yes, this is solved by allowing the specific script (which?) to run for that page. I generally just leave the page as it is, showing funny characters instead of the intended icons.
Re:Font Awesome 4.1 released by thatthatis on Saturday May 17, 2014 @01:09PM (#7760626)
Serious question: At this point, when you use noscript, don't you expect the web to be broken more places than not?
Re:Font Awesome 4.1 released by Yetanfou on Saturday May 17, 2014 @01:50PM (#7760711)
Serious answer: those sites which insist on being unusable for those who don't run scripts - be it those running text-based browsers of those who block scripts - are not worth visiting in my not that humble opinion.

I deem a site to be usable when the content can be read. Sometimes this means scrolling through an un-styled list of links and sundry before I can read whatever the site tries to convey. So be it.

Re:Font Awesome 4.1 released by sampk on Saturday May 17, 2014 @03:14PM (#7760782)
What scripts? The topic at hand is usage of custom fonts. Should we use images instead to please you?
Re:Font Awesome 4.1 released by TheLoneWolfling on Saturday May 17, 2014 @11:32AM (#7760403)
I'm one of six, apparently.
Re:Font Awesome 4.1 released by dfan on Saturday May 17, 2014 @11:43AM (#7760444)
Make it six or seven.
Re:Font Awesome 4.1 released by binaryanomaly on Saturday May 17, 2014 @10:32AM (#7760215)
hehe ;)