Comments on: Declarative AJAX Components and XML Namespaces

By: Dave Johnson

Dave Johnson — Thu, 14 Dec 2006 21:15:48 +0000

sorry faris but it looks like you will need to encode your html there.

I agree with your frustration! I have also found in proper XHTML that Firefox cannot get across the elements with different namesaces (using something like parentNode).

By: faris

faris — Thu, 14 Dec 2006 01:16:44 +0000

I actually have ran into the FireFox parsing issue that Dave described above and can’t really get it to work as expected. Even if you fully describe an extended DTD (according to W3C spec http://www.w3.org/TR/1999/xhtml-modularization-19990406/developing.html), it will not do the parsing as expected.

For example: something like

Will get parsed as:

It is really annoying and frustrating since we are always praising FireFox for following W3C standards but in fact it fails to comply just like IE in certain ways. At least IE does not comply in certain cases to make our live easiers, not worst!

By: Dave Johnson

Dave Johnson — Mon, 30 Oct 2006 18:10:02 +0000

thanks for the useful comments everyone!

Mark, thanks for the link to @role – very interesting point about accessibility as well.

Daniel, there are other browsers aside from FF and IE??? I personally have checked it out but now that I have a nice mac on my desktop i will be looking into Safari some more.

Hakan, I have not observed any problems drawing custom namespaces in IE7 but that is likely only because I have not been playing with it that much

By: Hakan Bilgin

Hakan Bilgin — Mon, 30 Oct 2006 11:08:13 +0000

Hey Dave,
Great post…

Have you or anyone else noticed that IE7 fails to redraw custom namespaces correctly, when swapping CSS-link? That is, without reloading the page (Firefox accomplishes this galantly).

I suspect that this problem is similar to hasLayout problem from IE6.

By: Daniel E. Renfer

Daniel E. Renfer — Fri, 20 Oct 2006 13:59:49 +0000

I’m curious, how do the other browsers out there (Safari, Opera, Dave’s Cool Browser 3.0, etc.) deal with these issues?

By: Mark Birbeck

Mark Birbeck — Fri, 20 Oct 2006 12:05:29 +0000

Good article Dave.

I don’t see a need for an “OpenAjax type” attribute, when the ‘role’ attribute from the W3C is ideal for what you are talking about: see Using role to extend XHTML.

Note also that @role is already supported in Firefox as a hook for accessibility: see Accessible DHTML. Of course, even if the browser doesn’t do anything with the attribute itself, there is nothing to prevent libraries like Dojo from using it as their hook.

Regards,

Mark

Mark Birbeck
http://www.formsPlayer.com/
http://skimstone.x-port.net/

By: Web Things, by Mark Baker » Blog Archive » Declarative Ajax catching on

Thu, 19 Oct 2006 20:10:42 +0000

[...] Declaritive Ajax components and XML namespaces, referencing a great Dave Johnson post. [...]

By: Dave Johnson

Dave Johnson — Tue, 17 Oct 2006 07:34:38 +0000

haha, forgot to escape those tags. oops.

-dave

By: Andre Charland

Andre Charland — Tue, 17 Oct 2006 07:30:49 +0000

Dave you’re always causing shit eh;-)

Hey there appears to be some content missing in FF after the lines:

“The big problem we have found is that Mozilla does not support self closing tags. One would expect that the following would be equivalent:”

Just an FYI.

By: Dave Johnson

Dave Johnson — Tue, 17 Oct 2006 05:38:41 +0000

Yeah i agree