There is a difference between legitimate differences in behavior between browsers (which GWT will try to shield you from) and outright bugs in one specific browser (that should be fixed in that browser). What you described sounded like an actual bug in FireFox, so it should be addressed at that level. IOW, we don't feel that it is GWT's mission to fix every bug in every browser.
OTOH, if you can show that the behavior you are seeing is caused by an actual bug in GWT itself (maybe bad JS generation under FF in this case), it would be something we would want to address at the GWT level. On Monday, March 5, 2012 3:05:39 AM UTC-5, eg wrote: > > I filed a bug with respect to a NamedFrame issue in FF (issue 7185). > > The bug was marked invalid with this remark: > 'Sounds like a browser quirk. Can you please ask this question on the > GWT user forum. It's not clear that this is a bug.' > > I thought one of the main points of GWT is that you wouldn't have to > deal with the quirkiness of different browsers! Since this issue works > in chrome and not in firefox i thought it was a bug! > > Maybe someone can explain if this is a bug or not? > > (I did find a work around so its not hugely urgent, but it still would > be nice to know!) > > Thanks > EG -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/Z1q2sNkWsxoJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
