I definitely agree that this is a big issue. We've discussed this before but were unclear as to the ramifications of not attaching anything to these specific elements. Although since code is breaking it definitely takes a high priority for us.
I'm not sure if the code to handle this should be in jQuery.data or outside of it. I'm worried that if it's inside it'll significantly slow down the number of cases where the method is referenced. At the very least we've already resolved the unload issue in the nightlies - it's just a matter of attempting to fix the other issues at play (events, selectors, and hide/show mostly). --John On Wed, Oct 29, 2008 at 12:21 PM, Valentin <[EMAIL PROTECTED]> wrote: > > As some of you know JQuery (as well as Prototype -- this was initially > one of the reasons for switching) has serious issues when dealing with > the <object>, <embed> or <applet> tags. > > If one decides to be XHTML 1.0 strict compliant we have to use the > <object> tag right now for Java applets, Flash movies, and other such > stuff. > > But because of a bug in the internal code of Jquery (namely this one: > http://dev.jquery.com/ticket/2349 ) we can't really use something > like > > $('#id_of_object').hide() or even stuff that's relative to the applet > (so say your applet has external function such as applet.Render() we > can't use $('#id_of_object').Render() ) > > Since the upcoming XHTML 2.0 Specs will require pretty much everything > but text to be inside an object tag I'm curious when this problem is > going to be solved and how ... > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jQuery Development" 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/jquery-dev?hl=en -~----------~----~----~----~------~----~------~--~---
