[Lift] Re: Firefox issue: anybody seen this?
Greetings mr Biggs, I would humbly suggest using Tools-Clear private data-mark Cache only and then press Clear private data now Then Refresh the page. I've been running into weird firefox caching issues since upgrading to FF 3. (This may or may not help) Also, try doing a view source and copy-n-paste the jquery.js URI into a new tab and see if it gets served. cheers, Viktor On Mon, Jan 19, 2009 at 4:52 PM, E. Biggs tacoban...@gmail.com wrote: Hello, So I'm getting an error on liftajax.js() [Line 110] in firefox saying jQuery is not defined. I'm puzzled because it works just fine safari, and the AJAX Samples on demo.liftweb.net works fine for me in firefox - and the order the scripts are included in the head are the same as my code... namely jQuery is included before liftajax. I even went to /classpath/jquery.js to make sure it was getting served (which seemed redundant since it works fine in safari) and indeed jetty served the js up just fine. Anybody encounter this or have any ideas? Thanks -- Viktor Klang Senior Systems Analyst --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Firefox issue: anybody seen this?
Hey thanks for the suggestions.. although I figured out what my problem is and it's a bit frustrating... What happened was that lift, as you probably know is all about xhtml.. which is incompatible with google maps (supposedly because it doesn't support document.write or something supposedly?) So I was switching my MIME type to text/html... And everything was fine.. except that lift doesn't play super nice with html which doesn't like having self closing tags... So what was happening was Firefox, being an html stickler, will choke on self closing script tags while safari will gracefully accept them. Of course Firefox is happy if I just switch my MIME type back to application/xhtml+xml but then google maps is unhappy. So, as far as I can tell I'm not going to be able to support firefox unless either google accepts xhtml or lift is happier about gratuitous end tags... Anybody know of a simple workaround for the latter? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Firefox issue: anybody seen this?
Okay, If you want to render tags using the same mechanism that's used for rendering tags for IE, in Boot.scala: LiftRules.calcIEMode = () = true This will cause all browsers to have tags rendered as foo/foo rather than foo/ (except the br tag). Thanks, David On Mon, Jan 19, 2009 at 8:44 AM, E. Biggs tacoban...@gmail.com wrote: Hey thanks for the suggestions.. although I figured out what my problem is and it's a bit frustrating... What happened was that lift, as you probably know is all about xhtml.. which is incompatible with google maps (supposedly because it doesn't support document.write or something supposedly?) So I was switching my MIME type to text/html... And everything was fine.. except that lift doesn't play super nice with html which doesn't like having self closing tags... So what was happening was Firefox, being an html stickler, will choke on self closing script tags while safari will gracefully accept them. Of course Firefox is happy if I just switch my MIME type back to application/xhtml+xml but then google maps is unhappy. So, as far as I can tell I'm not going to be able to support firefox unless either google accepts xhtml or lift is happier about gratuitous end tags... Anybody know of a simple workaround for the latter? -- Lift, the simply functional web framework http://liftweb.net Collaborative Task Management http://much4.us Follow me: http://twitter.com/dpp Git some: http://github.com/dpp --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Firefox issue: anybody seen this?
I use Google maps (but very basically) on several sites with lift using XHTML 1.1 with no problem. What is it hassling you with? Chas. E. Biggs wrote: Hey thanks for the suggestions.. although I figured out what my problem is and it's a bit frustrating... What happened was that lift, as you probably know is all about xhtml.. which is incompatible with google maps (supposedly because it doesn't support document.write or something supposedly?) So I was switching my MIME type to text/html... And everything was fine.. except that lift doesn't play super nice with html which doesn't like having self closing tags... So what was happening was Firefox, being an html stickler, will choke on self closing script tags while safari will gracefully accept them. Of course Firefox is happy if I just switch my MIME type back to application/xhtml+xml but then google maps is unhappy. So, as far as I can tell I'm not going to be able to support firefox unless either google accepts xhtml or lift is happier about gratuitous end tags... Anybody know of a simple workaround for the latter? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
[Lift] Re: Firefox issue: anybody seen this?
David, Awesome this is probably just what I'm looking for, I'll give it a shot. Charles, I did make some assumptions with my diagnoses. The behavior I see is that when I change the MIME type to application/xhtml+xml I get a js error complaining that GMap2 is undefined. Combined with information on the net such as a href=http://groups.google.gm/group/Google-Maps- API/browse_thread/thread/7dfcbb080d929b81/6cf8fd021ca8e98bthis/a I made the assumption that that's my problem. I'd be interested to know if/how you get GMap2 to be defined under that MIME type though? On Jan 19, 10:04 am, Charles F. Munat c...@munat.com wrote: I use Google maps (but very basically) on several sites with lift using XHTML 1.1 with no problem. What is it hassling you with? Chas. E. Biggs wrote: Hey thanks for the suggestions.. although I figured out what my problem is and it's a bit frustrating... What happened was that lift, as you probably know is all about xhtml.. which is incompatible with google maps (supposedly because it doesn't support document.write or something supposedly?) So I was switching my MIME type to text/html... And everything was fine.. except that lift doesn't play super nice with html which doesn't like having self closing tags... So what was happening was Firefox, being an html stickler, will choke on self closing script tags while safari will gracefully accept them. Of course Firefox is happy if I just switch my MIME type back to application/xhtml+xml but then google maps is unhappy. So, as far as I can tell I'm not going to be able to support firefox unless either google accepts xhtml or lift is happier about gratuitous end tags... Anybody know of a simple workaround for the latter? --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups Lift group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~--~~~~--~~--~--~---
