+briansnat Posted February 27, 2010 Posted February 27, 2010 http://www.geocaching.com/seek/cache_detai...c2-3f18682efe05 Seems to work in IE but not in Firefox. At least not in FF 3.6
+pppingme Posted February 27, 2010 Posted February 27, 2010 Huh, interesting. No maps, no description, and sidebar and stuff are at the bottom. I'm running FF 3.0.18 and its not quite right on there either.
vagabond Posted February 27, 2010 Posted February 27, 2010 Huh, interesting. No maps, no description, and sidebar and stuff are at the bottom. I'm running FF 3.0.18 and its not quite right on there either. Getting the same in 3.5.8
+McB. Posted February 27, 2010 Posted February 27, 2010 (edited) I've seen this error on other cache pages as well, but I have not seen a pattern to when and why it appears besides Firefox being the only affected browser. There's something seriously wrong with the generated HTML, but there's no telling whether it's a server side or client side error. Edited February 27, 2010 by McB'
stebu Posted February 27, 2010 Posted February 27, 2010 The source shows that FF somehow misses the en of comment: <!-- Description Written By: t--bone --> <div class="UserSuppliedContent"> .... So all of short and long description are as comments! It might have something to do with the owner's nick "t--bone"
+Nathan Wert Posted February 27, 2010 Posted February 27, 2010 It works just fine on Google's Chrome. *shrug*
+McB. Posted February 27, 2010 Posted February 27, 2010 We can also see that the "Navigation" div is located inside the "yui-main" and "Content" divs, where it normally resides outside and on the same level as "yui-main".
+Lil Devil Posted February 27, 2010 Posted February 27, 2010 (edited) The source shows that FF somehow misses the en of comment: <!-- Description Written By: t--bone --> <div class="UserSuppliedContent"> .... So all of short and long description are as comments! It might have something to do with the owner's nick "t--bone" Actually, it's Firefox that's getting it right and all the other browsers are getting it wrong. Technically, according to the spec, the -- in the middle of t--bone is the end of the comment. Most browsers look for --> as the end of the comment, but that's wrong. Firefox is obeying the spec and using the first -- it finds. The 2nd -- (right before the > ) is the beginning of a new comment. Edited February 27, 2010 by Lil Devil
+Michael Posted February 27, 2010 Posted February 27, 2010 Based on Lil Devil's explanation I have done a little minor magic and "fixed" it for FF and it still shows right in IE8. I will get with Nate Monday and explain to him what I did so we can pass it along to the Dev team.
+Lil Devil Posted February 27, 2010 Posted February 27, 2010 Funny. I was in there with my reviewer account fixing it, too
Keystone Posted February 27, 2010 Posted February 27, 2010 This was reported to the developers last week. Thanks for the additional example!
Recommended Posts