[jquery-dev] Re: Namespace failure

2009-02-15 Thread John Resig
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

[jquery-dev] Re: Namespace failure

2009-02-15 Thread Anko Painting
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 wrote: > Correct - you have to do it with the mimetype - which forces it in to

[jquery-dev] Re: Namespace failure

2009-02-13 Thread John Resig
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 wrote: > > http://media.nodnod.net/test.html works for me. Is it because I'm not > serving the page as application/xhtml+xml?

[jquery-dev] Re: Namespace failure

2009-02-13 Thread David Zhou
http://media.nodnod.net/test.html works for 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 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

[jquery-dev] Re: Namespace failure

2009-02-13 Thread Dave Methvin
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) --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "jQuery Development" group. To post to this gr

[jquery-dev] Re: Namespace failure

2009-02-13 Thread John Resig
> In that link, I see the alert from catch in Firefox 3 with the same > failure code that David mentioned earlier. Well, the difference should be that the error isn't coming from jQuery - this is purely a DOM/Firefox weird interaction here. It looks like its rejecting the namespace - and because

[jquery-dev] Re: Namespace failure

2009-02-13 Thread David Zhou
In that link, I see the alert from catch in Firefox 3 with the same failure code that David mentioned earlier. -- dz On Fri, Feb 13, 2009 at 9:15 AM, John Resig wrote: > > I've set up a test page and no possible combination that I try works: > http://dev.jquery.com/~john/ticket/xmlns/ > > In

[jquery-dev] Re: Namespace failure

2009-02-13 Thread John Resig
I've set up a test page and no possible combination that I try works: http://dev.jquery.com/~john/ticket/xmlns/ Including the basic one: var div = document.createElement("div"); div.innerHTML = 'Hi'; It sounds like there's another issue at play. --John On Fri, Feb 13, 2009 at 12:43 AM, David

[jquery-dev] Re: Namespace failure

2009-02-12 Thread David Pollak
I set a breakpoint at line 899 and inspected the div variable. It seems to be bound a phantom document that does not have any attributes (e.g., the xmlns:lift="..." attribute). This div is created in line 850 (div = context.createElement("div");) Hope this helps. On Feb 12, 9:24 pm, David Poll

[jquery-dev] Re: Namespace failure

2009-02-12 Thread David Pollak
On Feb 12, 7:37 pm, John Resig wrote: > I'm trying to figure out if this is something that's blockUI-specific. > What happens if you do: > $("#hi").html('Hi'); That fails in the same way on line 899 of jQuery 1.3.1. > > Inside your try/catch. > > --John > > On Thu, Feb 12, 2009 at 10:08 PM, D

[jquery-dev] Re: Namespace failure

2009-02-12 Thread John Resig
I'm trying to figure out if this is something that's blockUI-specific. What happens if you do: $("#hi").html('Hi'); Inside your try/catch. --John On Thu, Feb 12, 2009 at 10:08 PM, David Pollak wrote: > > > > On Feb 12, 6:09 pm, John Resig wrote: >> > "application/xhtml+xml" >> >> What do yo

[jquery-dev] Re: Namespace failure

2009-02-12 Thread David Pollak
On Feb 12, 6:09 pm, John Resig wrote: > > "application/xhtml+xml" > > What do you do for the other browsers? (IE) The XHTML is sent through a quirks mode rewriter for IE and served as text/html > > >> 2) Self-closing script tags are invalid (may want to fix those first). > > > Why are they in

[jquery-dev] Re: Namespace failure

2009-02-12 Thread John Resig
> "application/xhtml+xml" What do you do for the other browsers? (IE) >> 2) Self-closing script tags are invalid (may want to fix those first). > > Why are they invalid for xhtml? Dunno, but they are: http://www.w3.org/TR/xhtml1/#C_3 --John --~--~-~--~~~---~--~

[jquery-dev] Re: Namespace failure

2009-02-12 Thread David Pollak
On Feb 12, 1:49 pm, John Resig wrote: > 1) What mimetype are you serving this with? "application/xhtml+xml" > 2) Self-closing script tags are invalid (may want to fix those first). Why are they invalid for xhtml? > > --John > > On Thu, Feb 12, 2009 at 1:43 PM, David Pollak > > wrote: > > >

[jquery-dev] Re: Namespace failure

2009-02-12 Thread John Resig
1) What mimetype are you serving this with? 2) Self-closing script tags are invalid (may want to fix those first). --John On Thu, Feb 12, 2009 at 1:43 PM, David Pollak wrote: > > Folks, > > I use and *love* jQuery. I also run the Lift web framework project. > In Lift, we use jQuery and we us

[jquery-dev] Re: Namespace failure

2009-02-12 Thread David Pollak
On Feb 12, 10:49 am, Leonardo Rossetti wrote: > what is the purpose of this try-catch block? To catch and display the exception. If the try/catch block is omitted, the problem still ocurs, but is silently discarded (unless you've got Firebug running.) > > 2009/2/12 David Pollak > > > > > >

[jquery-dev] Re: Namespace failure

2009-02-12 Thread Leonardo Rossetti
what is the purpose of this try-catch block? 2009/2/12 David Pollak > > Folks, > > I use and *love* jQuery. I also run the Lift web framework project. > In Lift, we use jQuery and we use XHTML namespaces (we need to > decorate certain XHTML elements with lift:gc attributes.) > > We've run into