Declined
Last Updated: 11 Oct 2017 08:31 by ADMIN
Steve
Created on: 19 Jun 2013 13:45
Category: UI for ASP.NET AJAX
Type: Feature Request
15
FontAwesome Skin
You're working on a cleaner css3 approach, however sprites are still resource being downloaded...it's be great if the controls we're using on our page had iconography consistent with the site theme *automatically* instead of needing to use a custom skin.

Can you please implement a clean fontawesome enabled skin?  So instead of referencing a sprite and background position you instead would set :before or :after and content="\f002".

This makes the resulting resources much lighter...as there's no sprite (retina ready by default)

...it'd be up to us to have fontawesome loaded on our page.

(Teampulse uses fontawesome, and they have at least 1 radgrid)

http://fortawesome.github.io/Font-Awesome/icons/

Steve
(Total attached files size should be smaller than 20mb. Allowed extensions: .zip, .rar, .jpg, .png, .gif)
4 comments
ADMIN
Marin Bratanov
Posted on: 11 Oct 2017 08:31
The Lightweight RenderMode uses font icons and only a few raster images (mostly animated loading signs). Thus, all skins are font-icons-enabled.
Murray
Posted on: 08 Jun 2016 01:10
I LOVE this suggestion! Thank you Steve. I would also ask that the skin still be made accessible - especially to those using screen readers.
Steve
Posted on: 20 Jun 2013 08:52
Fontawseome has ie7 support...so either use javascript to add in physical elements on ie7, or the more likely scenario...just stop supporting ie7 on the skin or globally.

Browser has 0.8 or less marketshare, so low that users already voted out ie7 support on kendo...and there has been zero public outcry.

If I'm the developer it's up to me to know the requirements for a site.  If I'm using bootstrap and doing a modern css3 site...I'm likely already deciding to not bother with ie7 :)
ADMIN
Ivan Zhekov
Posted on: 20 Jun 2013 08:23
But what of the cons? Of course in modern browsers everything will look fancy as it should, but that wouldn't be the case for older browsers.

As a start, :before is supported from IE8 plus and while we may want to think IE browser below version 8 does not exist, that's quite far from the truth -- there is compatibility mode.

That said, the idea is a good one.