Hi Chris, The issue is 'font size' and not 'font-render-path'. The problem is that font-size in development mode is incorrect and only in Firefox; when viewing font-size info in Firefox Firebug it clearly shows a value other than what is declared in the css declarations.
Firebug always shows that font-size is a fraction of what I declared it to be (in pixels). I am guessing that when in development mode and targeting Firefox GWT defaults to using em units internally for font sizes and then converts them back to pixels. Why? Who knows! Perhaps, though, it is because of some optimizing issues specific to Firefox. I appreciate your input, Chris. As this is still unresolved I would very much appreciate it if someone from the GWT team would take the time to address this. Thanks in advance. Jeff On Tue, Dec 14, 2010 at 10:53 AM, Chris Conroy <con...@google.com> wrote: > I don't see how devmode could affect the font render path. > > FWIW, you shouldn't need to use the production server to use the compiled > output. If you run a GWT compile and then hit your devmode server like usual > but strip the ?gwt.codesvr fragment, then the embedded Jetty will serve up > the version you just compiled. > > On Tue, Dec 14, 2010 at 6:47 AM, Jeff Schwartz <jefftschwa...@gmail.com>wrote: > >> Hi All, >> >> When viewing rendered pages in Firefox while in development mode my font >> sizes are being transposed. For instance, if I specify a font size of 12px >> in my uibinder xml's style declarations it is actually rendered as 10.7833px >> with other similar transpositions for other font-sizes.This appears to only >> be an issue with Firefox (I am running the latest release for Windows Vista) >> and font sizes render accurately in development mode for the latest releases >> of Chrome, Safari and MS IE. >> >> This makes testing in development mode very inconvenient on Firefox to put >> it mildly as it forces me to have to run it on the production server in >> order to get an accurate rendering which is something I will not be able to >> do once the application goes live. >> >> Any clues on this? Is this a known issue? Is there something I can do >> code-wise to have fonts rendered accurately? >> >> Thank you. >> >> -- >> *Jeff Schwartz* >> >> -- >> You received this message because you are subscribed to the Google Groups >> "Google Web Toolkit" group. >> To post to this group, send email to google-web-tool...@googlegroups.com. >> To unsubscribe from this group, send email to >> google-web-toolkit+unsubscr...@googlegroups.com<google-web-toolkit%2bunsubscr...@googlegroups.com> >> . >> For more options, visit this group at >> http://groups.google.com/group/google-web-toolkit?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups > "Google Web Toolkit" group. > To post to this group, send email to google-web-tool...@googlegroups.com. > To unsubscribe from this group, send email to > google-web-toolkit+unsubscr...@googlegroups.com<google-web-toolkit%2bunsubscr...@googlegroups.com> > . > For more options, visit this group at > http://groups.google.com/group/google-web-toolkit?hl=en. > -- *Jeff Schwartz* -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
