On Jul 29, 10:13 pm, James McMinn <cyb...@gmail.com> wrote: > > I'll need to keep that in mind, it never occurred to me that Firefox would > do that.
I did a bit of research and it's confirmed as a bug in Firefox since 2003 and the reason it's not been fixed is performance (some aspect of rendering performance is O(n^2) on length of text) https://bugzilla.mozilla.org/show_bug.cgi?id=194231 another solution says to use the Mozilla-specific "textContent" attribute: http://www.coderholic.com/firefox-4k-xml-node-limit/ and it seems it's an open issue with GWT since 2007 http://code.google.com/p/google-web-toolkit/issues/detail?id=719 ... -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. To post to this group, send email to google-maps-js-api...@googlegroups.com. To unsubscribe from this group, send email to google-maps-js-api-v3+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
