I should add one note that although the code compiles without warning, it does not guarantee that the font will have downloaded before the content is displayed to the user. So there is still the possibility that users will see fallback fonts until the webfont has downloaded.
Other than inlining the data resource, I don't know that there's anything to do about that issue. The fonts I'm using are 30k-50k compressed, so I don't know if it's worth trying to inline them. On 2010/10/10 02:57:49, jcarlson wrote:
My knowledge and familiarity with the workings of how CssResources are
generated
is shallow, but I applied the patch here to my project and was able to
compile a
module that used @font-face in the CSS.
As described in the bug report (http://code.google.com/p/google-web-toolkit/issues/detail?id=5247),
this patch
worked for me.
http://gwt-code-reviews.appspot.com/943802/show -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
