[Lift] Re: Fwd: [jquery-dev] Re: Namespace failure
What's the impact overall? Is this a result of upgrade to JQuery 1.3.1? Thanks, Tim On Feb 16, 4:51 pm, David Pollak feeder.of.the.be...@gmail.com wrote: Folks, It turns out that there are issues with jQuery's methods that insert/replace HTML and using XHTML on Firefox. Sigh. We should be aware of this. using $(...).html(stuff) will likely fail if any of the elements in stuff have namespaces. Sorry. David -- Forwarded message -- From: John Resig jere...@gmail.com Date: Sun, Feb 15, 2009 at 8:31 PM Subject: [jquery-dev] Re: Namespace failure To: jquery-...@googlegroups.com Anko - You're welcome to file a bug on XHTML support - let me know when you do. I have it penciled in the Roadmap for jQuery 1.4 - but it's going to require a lot of work (basic things like innerHTML aren't guaranteed to work, for example) - not to mention that things like attributes and expandos are handled very differently. I took some very basic steps of converting our test suite to run under the proper mimetype and wasn't terribly pleased with the result (lots of failures). I'll definitely revisit it at some point, though. Right now the only component guaranteed I'm sure that passes is the selector engine. I'd like to have 100% passing in all components for 1.4. http://dev.jquery.com/browser/trunk/jquery/test/xhtml.php --John On Sun, Feb 15, 2009 at 9:24 PM, Anko Painting anko@gmail.com wrote: Is there a ticket associated with this bug? I'm dealing with the same issue myself. It's frustrating because i need to serve as application/xhtml+xml so that I can put svg on the page. On Feb 14, 12:52 am, John Resig jere...@gmail.com wrote: Correct - you have to do it with the mimetype - which forces it in to the XML mode where everything becomes 'fun'. --John On Fri, Feb 13, 2009 at 9:37 AM, David Zhou da...@nodnod.net wrote: http://media.nodnod.net/test.htmlworksfor me. Is it because I'm not serving the page as application/xhtml+xml? -- dz On Fri, Feb 13, 2009 at 9:31 AM, Dave Methvin dave.meth...@gmail.com wrote: Me too. Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.6) Gecko/ 2009011913 Firefox/3.0.6 (.NET CLR 3.5.30729) -- Lift, the simply functional web frameworkhttp://liftweb.net Beginning Scalahttp://www.apress.com/book/view/1430219890 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: Fwd: [jquery-dev] Re: Namespace failure
On Mon, Feb 16, 2009 at 9:04 AM, Tim Perrett he...@timperrett.com wrote: What's the impact overall? The impact is: use innerHTML directly rather than going through jQuery's HTML re-writing. Is this a result of upgrade to JQuery 1.3.1? No. This is a latent Firefox bug and has to do with how jQuery sanitizes HTML. The problem existed in prior versions of jQuery, but is now an issue because of the lift:gc stuff. Thanks, Tim On Feb 16, 4:51 pm, David Pollak feeder.of.the.be...@gmail.com wrote: Folks, It turns out that there are issues with jQuery's methods that insert/replace HTML and using XHTML on Firefox. Sigh. We should be aware of this. using $(...).html(stuff) will likely fail if any of the elements in stuff have namespaces. Sorry. David -- Forwarded message -- From: John Resig jere...@gmail.com Date: Sun, Feb 15, 2009 at 8:31 PM Subject: [jquery-dev] Re: Namespace failure To: jquery-...@googlegroups.com Anko - You're welcome to file a bug on XHTML support - let me know when you do. I have it penciled in the Roadmap for jQuery 1.4 - but it's going to require a lot of work (basic things like innerHTML aren't guaranteed to work, for example) - not to mention that things like attributes and expandos are handled very differently. I took some very basic steps of converting our test suite to run under the proper mimetype and wasn't terribly pleased with the result (lots of failures). I'll definitely revisit it at some point, though. Right now the only component guaranteed I'm sure that passes is the selector engine. I'd like to have 100% passing in all components for 1.4. http://dev.jquery.com/browser/trunk/jquery/test/xhtml.php --John On Sun, Feb 15, 2009 at 9:24 PM, Anko Painting anko@gmail.com wrote: Is there a ticket associated with this bug? I'm dealing with the same issue myself. It's frustrating because i need to serve as application/xhtml+xml so that I can put svg on the page. On Feb 14, 12:52 am, John Resig jere...@gmail.com wrote: Correct - you have to do it with the mimetype - which forces it in to the XML mode where everything becomes 'fun'. --John On Fri, Feb 13, 2009 at 9:37 AM, David Zhou da...@nodnod.net wrote: http://media.nodnod.net/test.htmlworksfor me. Is it because I'm not serving the page as application/xhtml+xml? -- dz On Fri, Feb 13, 2009 at 9:31 AM, Dave Methvin dave.meth...@gmail.com wrote: Me too. Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.6) Gecko/ 2009011913 Firefox/3.0.6 (.NET CLR 3.5.30729) -- Lift, the simply functional web frameworkhttp://liftweb.net Beginning Scalahttp://www.apress.com/book/view/1430219890 Follow me:http://twitter.com/dpp Git some:http://github.com/dpp -- 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 --~--~-~--~~~---~--~~ 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: Fwd: [jquery-dev] Re: Namespace failure
How about adding a class-attribute called gc to everything that's supposedly collectible? Then doing a scrape using jQuery(.gc) would be just as feasible. Would it solve the problem or can it be extended to solve it fully? On Mon, Feb 16, 2009 at 10:37 PM, David Pollak feeder.of.the.be...@gmail.com wrote: On Mon, Feb 16, 2009 at 1:36 PM, Jorge Ortiz jorge.or...@gmail.comwrote: Can lift:gc be renamed lift_gc until the bug is addressed? lift_gc is not a valid attribute in XHTML as far as I know, so browsers would reject any element containing that attribute. :-( On Mon, Feb 16, 2009 at 9:20 AM, David Pollak feeder.of.the.be...@gmail.com wrote: On Mon, Feb 16, 2009 at 9:04 AM, Tim Perrett he...@timperrett.comwrote: What's the impact overall? The impact is: use innerHTML directly rather than going through jQuery's HTML re-writing. Is this a result of upgrade to JQuery 1.3.1? No. This is a latent Firefox bug and has to do with how jQuery sanitizes HTML. The problem existed in prior versions of jQuery, but is now an issue because of the lift:gc stuff. Thanks, Tim On Feb 16, 4:51 pm, David Pollak feeder.of.the.be...@gmail.com wrote: Folks, It turns out that there are issues with jQuery's methods that insert/replace HTML and using XHTML on Firefox. Sigh. We should be aware of this. using $(...).html(stuff) will likely fail if any of the elements in stuff have namespaces. Sorry. David -- Forwarded message -- From: John Resig jere...@gmail.com Date: Sun, Feb 15, 2009 at 8:31 PM Subject: [jquery-dev] Re: Namespace failure To: jquery-...@googlegroups.com Anko - You're welcome to file a bug on XHTML support - let me know when you do. I have it penciled in the Roadmap for jQuery 1.4 - but it's going to require a lot of work (basic things like innerHTML aren't guaranteed to work, for example) - not to mention that things like attributes and expandos are handled very differently. I took some very basic steps of converting our test suite to run under the proper mimetype and wasn't terribly pleased with the result (lots of failures). I'll definitely revisit it at some point, though. Right now the only component guaranteed I'm sure that passes is the selector engine. I'd like to have 100% passing in all components for 1.4. http://dev.jquery.com/browser/trunk/jquery/test/xhtml.php --John On Sun, Feb 15, 2009 at 9:24 PM, Anko Painting anko@gmail.com wrote: Is there a ticket associated with this bug? I'm dealing with the same issue myself. It's frustrating because i need to serve as application/xhtml+xml so that I can put svg on the page. On Feb 14, 12:52 am, John Resig jere...@gmail.com wrote: Correct - you have to do it with the mimetype - which forces it in to the XML mode where everything becomes 'fun'. --John On Fri, Feb 13, 2009 at 9:37 AM, David Zhou da...@nodnod.net wrote: http://media.nodnod.net/test.htmlworksfor me. Is it because I'm not serving the page as application/xhtml+xml? -- dz On Fri, Feb 13, 2009 at 9:31 AM, Dave Methvin dave.meth...@gmail.com wrote: Me too. Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.6) Gecko/ 2009011913 Firefox/3.0.6 (.NET CLR 3.5.30729) -- Lift, the simply functional web frameworkhttp://liftweb.net Beginning Scalahttp://www.apress.com/book/view/1430219890 Follow me:http://twitter.com/dpp Git some:http://github.com/dpp -- 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 -- 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 -- 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: Fwd: [jquery-dev] Re: Namespace failure
what would the raw XHTML look like? Also, we can't rely on jQuery to scrape because we have to support other libraries (e.g., YUI) without jQuery. On Mon, Feb 16, 2009 at 1:45 PM, Viktor Klang viktor.kl...@gmail.comwrote: How about adding a class-attribute called gc to everything that's supposedly collectible? Then doing a scrape using jQuery(.gc) would be just as feasible. Would it solve the problem or can it be extended to solve it fully? On Mon, Feb 16, 2009 at 10:37 PM, David Pollak feeder.of.the.be...@gmail.com wrote: On Mon, Feb 16, 2009 at 1:36 PM, Jorge Ortiz jorge.or...@gmail.comwrote: Can lift:gc be renamed lift_gc until the bug is addressed? lift_gc is not a valid attribute in XHTML as far as I know, so browsers would reject any element containing that attribute. :-( On Mon, Feb 16, 2009 at 9:20 AM, David Pollak feeder.of.the.be...@gmail.com wrote: On Mon, Feb 16, 2009 at 9:04 AM, Tim Perrett he...@timperrett.comwrote: What's the impact overall? The impact is: use innerHTML directly rather than going through jQuery's HTML re-writing. Is this a result of upgrade to JQuery 1.3.1? No. This is a latent Firefox bug and has to do with how jQuery sanitizes HTML. The problem existed in prior versions of jQuery, but is now an issue because of the lift:gc stuff. Thanks, Tim On Feb 16, 4:51 pm, David Pollak feeder.of.the.be...@gmail.com wrote: Folks, It turns out that there are issues with jQuery's methods that insert/replace HTML and using XHTML on Firefox. Sigh. We should be aware of this. using $(...).html(stuff) will likely fail if any of the elements in stuff have namespaces. Sorry. David -- Forwarded message -- From: John Resig jere...@gmail.com Date: Sun, Feb 15, 2009 at 8:31 PM Subject: [jquery-dev] Re: Namespace failure To: jquery-...@googlegroups.com Anko - You're welcome to file a bug on XHTML support - let me know when you do. I have it penciled in the Roadmap for jQuery 1.4 - but it's going to require a lot of work (basic things like innerHTML aren't guaranteed to work, for example) - not to mention that things like attributes and expandos are handled very differently. I took some very basic steps of converting our test suite to run under the proper mimetype and wasn't terribly pleased with the result (lots of failures). I'll definitely revisit it at some point, though. Right now the only component guaranteed I'm sure that passes is the selector engine. I'd like to have 100% passing in all components for 1.4. http://dev.jquery.com/browser/trunk/jquery/test/xhtml.php --John On Sun, Feb 15, 2009 at 9:24 PM, Anko Painting anko@gmail.com wrote: Is there a ticket associated with this bug? I'm dealing with the same issue myself. It's frustrating because i need to serve as application/xhtml+xml so that I can put svg on the page. On Feb 14, 12:52 am, John Resig jere...@gmail.com wrote: Correct - you have to do it with the mimetype - which forces it in to the XML mode where everything becomes 'fun'. --John On Fri, Feb 13, 2009 at 9:37 AM, David Zhou da...@nodnod.net wrote: http://media.nodnod.net/test.htmlworksfor me. Is it because I'm not serving the page as application/xhtml+xml? -- dz On Fri, Feb 13, 2009 at 9:31 AM, Dave Methvin dave.meth...@gmail.com wrote: Me too. Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.6) Gecko/ 2009011913 Firefox/3.0.6 (.NET CLR 3.5.30729) -- Lift, the simply functional web frameworkhttp://liftweb.net Beginning Scalahttp://www.apress.com/book/view/1430219890 Follow me:http://twitter.com/dpp Git some:http://github.com/dpp -- 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 -- 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 -- Viktor Klang Senior Systems Analyst -- 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 --~--~-~--~~~---~--~~ 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: Fwd: [jquery-dev] Re: Namespace failure
This might be a bit of a pain to deal with, but something like: tag class=lift-gc lift-gc-[uuid] / Of course, you'd want to append to the 'class' attribute, not replace it entirely. --j On Mon, Feb 16, 2009 at 1:49 PM, David Pollak feeder.of.the.be...@gmail.com wrote: what would the raw XHTML look like? Also, we can't rely on jQuery to scrape because we have to support other libraries (e.g., YUI) without jQuery. On Mon, Feb 16, 2009 at 1:45 PM, Viktor Klang viktor.kl...@gmail.comwrote: How about adding a class-attribute called gc to everything that's supposedly collectible? Then doing a scrape using jQuery(.gc) would be just as feasible. Would it solve the problem or can it be extended to solve it fully? On Mon, Feb 16, 2009 at 10:37 PM, David Pollak feeder.of.the.be...@gmail.com wrote: On Mon, Feb 16, 2009 at 1:36 PM, Jorge Ortiz jorge.or...@gmail.comwrote: Can lift:gc be renamed lift_gc until the bug is addressed? lift_gc is not a valid attribute in XHTML as far as I know, so browsers would reject any element containing that attribute. :-( On Mon, Feb 16, 2009 at 9:20 AM, David Pollak feeder.of.the.be...@gmail.com wrote: On Mon, Feb 16, 2009 at 9:04 AM, Tim Perrett he...@timperrett.comwrote: What's the impact overall? The impact is: use innerHTML directly rather than going through jQuery's HTML re-writing. Is this a result of upgrade to JQuery 1.3.1? No. This is a latent Firefox bug and has to do with how jQuery sanitizes HTML. The problem existed in prior versions of jQuery, but is now an issue because of the lift:gc stuff. Thanks, Tim On Feb 16, 4:51 pm, David Pollak feeder.of.the.be...@gmail.com wrote: Folks, It turns out that there are issues with jQuery's methods that insert/replace HTML and using XHTML on Firefox. Sigh. We should be aware of this. using $(...).html(stuff) will likely fail if any of the elements in stuff have namespaces. Sorry. David -- Forwarded message -- From: John Resig jere...@gmail.com Date: Sun, Feb 15, 2009 at 8:31 PM Subject: [jquery-dev] Re: Namespace failure To: jquery-...@googlegroups.com Anko - You're welcome to file a bug on XHTML support - let me know when you do. I have it penciled in the Roadmap for jQuery 1.4 - but it's going to require a lot of work (basic things like innerHTML aren't guaranteed to work, for example) - not to mention that things like attributes and expandos are handled very differently. I took some very basic steps of converting our test suite to run under the proper mimetype and wasn't terribly pleased with the result (lots of failures). I'll definitely revisit it at some point, though. Right now the only component guaranteed I'm sure that passes is the selector engine. I'd like to have 100% passing in all components for 1.4. http://dev.jquery.com/browser/trunk/jquery/test/xhtml.php --John On Sun, Feb 15, 2009 at 9:24 PM, Anko Painting anko@gmail.com wrote: Is there a ticket associated with this bug? I'm dealing with the same issue myself. It's frustrating because i need to serve as application/xhtml+xml so that I can put svg on the page. On Feb 14, 12:52 am, John Resig jere...@gmail.com wrote: Correct - you have to do it with the mimetype - which forces it in to the XML mode where everything becomes 'fun'. --John On Fri, Feb 13, 2009 at 9:37 AM, David Zhou da...@nodnod.net wrote: http://media.nodnod.net/test.htmlworksfor me. Is it because I'm not serving the page as application/xhtml+xml? -- dz On Fri, Feb 13, 2009 at 9:31 AM, Dave Methvin dave.meth...@gmail.com wrote: Me too. Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.6) Gecko/ 2009011913 Firefox/3.0.6 (.NET CLR 3.5.30729) -- Lift, the simply functional web frameworkhttp://liftweb.net Beginning Scalahttp://www.apress.com/book/view/1430219890 Follow me:http://twitter.com/dpp Git some:http://github.com/dpp -- 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 -- 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 -- Viktor Klang Senior Systems Analyst -- 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 --~--~-~--~~~---~--~~ 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
[Lift] Re: Fwd: [jquery-dev] Re: Namespace failure
I wonder if 1,000 missing classes will cause the CSS engines to barf. Anyone want to mock up a page or two and feed them into IE6, etc.? On Mon, Feb 16, 2009 at 2:15 PM, Jorge Ortiz jorge.or...@gmail.com wrote: This might be a bit of a pain to deal with, but something like: tag class=lift-gc lift-gc-[uuid] / Of course, you'd want to append to the 'class' attribute, not replace it entirely. --j On Mon, Feb 16, 2009 at 1:49 PM, David Pollak feeder.of.the.be...@gmail.com wrote: what would the raw XHTML look like? Also, we can't rely on jQuery to scrape because we have to support other libraries (e.g., YUI) without jQuery. On Mon, Feb 16, 2009 at 1:45 PM, Viktor Klang viktor.kl...@gmail.comwrote: How about adding a class-attribute called gc to everything that's supposedly collectible? Then doing a scrape using jQuery(.gc) would be just as feasible. Would it solve the problem or can it be extended to solve it fully? On Mon, Feb 16, 2009 at 10:37 PM, David Pollak feeder.of.the.be...@gmail.com wrote: On Mon, Feb 16, 2009 at 1:36 PM, Jorge Ortiz jorge.or...@gmail.comwrote: Can lift:gc be renamed lift_gc until the bug is addressed? lift_gc is not a valid attribute in XHTML as far as I know, so browsers would reject any element containing that attribute. :-( On Mon, Feb 16, 2009 at 9:20 AM, David Pollak feeder.of.the.be...@gmail.com wrote: On Mon, Feb 16, 2009 at 9:04 AM, Tim Perrett he...@timperrett.comwrote: What's the impact overall? The impact is: use innerHTML directly rather than going through jQuery's HTML re-writing. Is this a result of upgrade to JQuery 1.3.1? No. This is a latent Firefox bug and has to do with how jQuery sanitizes HTML. The problem existed in prior versions of jQuery, but is now an issue because of the lift:gc stuff. Thanks, Tim On Feb 16, 4:51 pm, David Pollak feeder.of.the.be...@gmail.com wrote: Folks, It turns out that there are issues with jQuery's methods that insert/replace HTML and using XHTML on Firefox. Sigh. We should be aware of this. using $(...).html(stuff) will likely fail if any of the elements in stuff have namespaces. Sorry. David -- Forwarded message -- From: John Resig jere...@gmail.com Date: Sun, Feb 15, 2009 at 8:31 PM Subject: [jquery-dev] Re: Namespace failure To: jquery-...@googlegroups.com Anko - You're welcome to file a bug on XHTML support - let me know when you do. I have it penciled in the Roadmap for jQuery 1.4 - but it's going to require a lot of work (basic things like innerHTML aren't guaranteed to work, for example) - not to mention that things like attributes and expandos are handled very differently. I took some very basic steps of converting our test suite to run under the proper mimetype and wasn't terribly pleased with the result (lots of failures). I'll definitely revisit it at some point, though. Right now the only component guaranteed I'm sure that passes is the selector engine. I'd like to have 100% passing in all components for 1.4. http://dev.jquery.com/browser/trunk/jquery/test/xhtml.php --John On Sun, Feb 15, 2009 at 9:24 PM, Anko Painting anko@gmail.com wrote: Is there a ticket associated with this bug? I'm dealing with the same issue myself. It's frustrating because i need to serve as application/xhtml+xml so that I can put svg on the page. On Feb 14, 12:52 am, John Resig jere...@gmail.com wrote: Correct - you have to do it with the mimetype - which forces it in to the XML mode where everything becomes 'fun'. --John On Fri, Feb 13, 2009 at 9:37 AM, David Zhou da...@nodnod.net wrote: http://media.nodnod.net/test.htmlworksfor me. Is it because I'm not serving the page as application/xhtml+xml? -- dz On Fri, Feb 13, 2009 at 9:31 AM, Dave Methvin dave.meth...@gmail.com wrote: Me too. Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.6) Gecko/ 2009011913 Firefox/3.0.6 (.NET CLR 3.5.30729) -- Lift, the simply functional web frameworkhttp://liftweb.net Beginning Scalahttp://www.apress.com/book/view/1430219890 Follow me:http://twitter.com/dpp Git some:http://github.com/dpp -- 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 -- 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 -- Viktor Klang Senior Systems Analyst -- 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 -- Lift, the simply functional web framework
