David, i'm testing in FF and Safari. i get the very same behavior.
Best wishes, --greg On Wed, Feb 18, 2009 at 2:17 PM, David Pollak <[email protected] > wrote: > Greg, > I haven't had a chance to look at your code, but are you testing in > Firefox? > > Firefox has a very, very, very nasty bug related to XHTML namepsaces that's > further poked by jQuery. > > Marius is working on a fix and it should be out tomorrow. > > Please try Safari or Chrome for testing and see if the problems are the > same. > > Thanks, > > David > > > On Wed, Feb 18, 2009 at 2:07 PM, Meredith Gregory < > [email protected]> wrote: > >> Lifted, >> >> The test case i submitted for strange behavior also happens to be a >> regression test for 11-SNAPSHOT. If you compile and run the dspace test case >> under lift .10, at least the activity creation code works as expected. If >> you compile and run the dspace test case under lift 11-SNAPSHOT, the >> activity creation code does nothing at all. >> >> i'd roll back to 10, but for the fact that i need changes related to JPA. >> i can haz a clue? >> >> Best wishes, >> >> --greg >> >> On Fri, Feb 13, 2009 at 12:38 PM, Meredith Gregory < >> [email protected]> wrote: >> >>> Lifted, >>> >>> Attached is a minimal example of a strange interaction between lift and a >>> jQuery plugin. If you unzip the example you will find inside the >>> liftTestCase directory 5 subdirectories two of which contain behaviors to >>> compare. The directory 23 contains an example that is purely jQuery with the >>> EasyWidgets plugin. The directory dspace contains a lift-based site. >>> >>> If you open 23/index.html in a browser you will see a page that allows >>> you to add widgets that can be dragged and dropped around. This all works. >>> If you cd into dspace and launch mvn jetty:run, sign up, login, then you >>> will see a boiled down version of the same thing. The difference is that the >>> javascript jQuery call is run as a JsRaw. Everything seems to work except >>> you attempt to drag and drop the components. Then you get very weird >>> behavior that is easier to see than to describe. >>> >>> The thing is, we haven't actually done any interesting lift stuff, yet, >>> in the boiled down sample. We're just calling into the EasyWidgets function >>> just like in the sample. i would expect these two examples to exhibit nearly >>> identical behavior. i'm guessing there's some weird interaction between >>> lift-included javascript and the jQuery plugin. >>> >>> Several questions: >>> >>> - How could we devise a way to check at compile time that there is >>> such an interaction? This seems to be a crucial point as the momentum is >>> to >>> use third party frontend web components. >>> - What is the best way to go about finding the interaction if it has >>> escaped compile time detection? >>> >>> >>> Best wishes, >>> >>> --greg >>> >>> -- >>> L.G. Meredith >>> Managing Partner >>> Biosimilarity LLC >>> 806 55th St NE >>> Seattle, WA 98105 >>> >>> +1 206.650.3740 >>> >>> http://biosimilarity.blogspot.com >>> >> >> >> >> -- >> L.G. Meredith >> Managing Partner >> Biosimilarity LLC >> 806 55th St NE >> Seattle, WA 98105 >> >> +1 206.650.3740 >> >> http://biosimilarity.blogspot.com >> >> >> > > > -- > Lift, the simply functional web framework http://liftweb.net > Beginning Scala http://www.apress.com/book/view/1430219890 > Follow me: http://twitter.com/dpp > Git some: http://github.com/dpp > > > > -- L.G. Meredith Managing Partner Biosimilarity LLC 806 55th St NE Seattle, WA 98105 +1 206.650.3740 http://biosimilarity.blogspot.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. 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/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
