Open GoogleCodeExporter opened 9 years ago
Original comment by kpreid.switchb.org
on 10 Oct 2012 at 2:09
Google web fonts are great and should be available in HTMLservise and UIapp
Original comment by rudyleh...@gmail.com
on 25 Oct 2012 at 5:59
UiApp?? I think you're misunderstanding google-caja issue tracker with
apps-script.
Original comment by hgabreu
on 25 Oct 2012 at 6:47
I believe Rudy meant that since UiApp HtmlService relies|depend on Caja,
support for sanitization of web-fonts is a must have to build nice looking
sites using UiApps.
Original comment by pie...@vanacker.cc
on 25 Oct 2012 at 6:53
UiApp is one thing and HtmlService is another one. It seems you've also
confused it.
Apps Script HtmlService uses Google Caja behind the scenes, UiApp not! They're
just not the same thing.
Also, bringing this Apps Script terms into the Google Caja issue tracker
probably does not help. The googlers on the Caja team, that will eventually
work on this, probably does not know what we're talking about.
Original comment by hgabreu
on 25 Oct 2012 at 7:07
Right, only HtmlServices relies on Caja. I guess the confusion comes from the
two being often used together.
Let's stick to Caja supporting sanitization of font-data and ideally support
for Google Web-fonts!
Original comment by van...@iplanned.it
on 25 Oct 2012 at 8:18
Original comment by kpreid.switchb.org
on 25 Oct 2012 at 8:27
Although this is not the place, I can't help myself and have to clarify this
misconceptions again.
HtmlService and UiApp have the same goal, i.e. to build user interfaces
(actually HtmlService is way more powerful and can be used for more). But they
are *never* "used together". The script that uses one is forbidden to use the
other!
Original comment by hgabreu
on 25 Oct 2012 at 10:41
Yes, we want Google Fonts support in the htmlservice. Let's make the web
beautiful again!
Original comment by hodgson....@gmail.com
on 25 Sep 2013 at 12:32
Original comment by kpreid@google.com
on 11 Nov 2013 at 6:28
WebFont support would be very useful. We use FontAwesome and GlyphIcons for our
user interface outside of Apps Script, and we lose consistency in our Apps
Script interface because we can't distribute the interface icon fonts. Instead
we have to rasterize the icons as images, which means they don't scale cleanly,
have to be hosted somewhere (so adding a new icon means manual steps rather
than just using the font), etc.
Original comment by david-...@docsend.com
on 28 Jan 2014 at 9:26
I agree, support for @font-face sanitization and usability is a must. Like
several others have said, it would really help for UI look and feel.
Original comment by anolispo...@gmail.com
on 19 Feb 2014 at 6:20
What is the current status of implementing support for this feature into Caja?
Is it ever going to happen?
Original comment by matsdesw...@gmail.com
on 18 Apr 2014 at 3:27
I would love this as well! I can see a lot of support for it; is there any plan
for implementation?
Original comment by tris...@hcresearch.co
on 4 Jun 2014 at 7:16
Looking forward for the implementation.
Any news regarding this topic?
Original comment by sandoval...@gmail.com
on 9 Jun 2014 at 5:30
+1. I'm also looking forward to this. :)
Original comment by edw...@kaizena.com
on 30 Sep 2014 at 4:46
Hi All
I am trying to work on an Add-On to assist dyslexics so having the ability to
grab the right fonts in the side panel is key.
What I dont understand is why this works on a Linux Ubuntu desktop and not on a
Chromebook or windows7 desktop.
Original comment by jason.pe...@gmail.com
on 7 Oct 2014 at 9:22
I'm also looking forward to this. any updates regarding @font-face in caja ?
Original comment by webmun...@gmail.com
on 21 Oct 2014 at 6:48
+1 Looking forward for the implementation.
Original comment by Ohh...@gmail.com
on 21 Oct 2014 at 10:41
OK so coming back to add further comments.
I have a real need to ensure that the fonts within my add-on reflect the users
choice. How far off is this from being sorted please?
Could we get some feedback from the team.
Jason
Original comment by jason.pe...@gmail.com
on 7 Nov 2014 at 12:31
I'm in dire need of this as well. Can't believe this issue was posted in 2012
and still no support.
Are there any work-arounds?
Original comment by AlbertVo...@gmail.com
on 21 Mar 2015 at 1:42
Original issue reported on code.google.com by
van...@iplanned.it
on 10 Oct 2012 at 1:49