
23 Jun
2006
23 Jun
'06
9:41 a.m.
Hi Holger,
Holger Joukl wrote:
I meant that it was possible to have namespace-agnostic, per-tagname custom default classes (as opposed to namespace-aware per-tagname custom classes), but admit I don't really have any usecase for that.
And admittedly your solution and API is nice and clean.
I already had such a thing in the back of my head for a while, so it didn't come as a surprise. I just wasn't quite sure how to get it straight. Your proposal assured me that a utility function is the way to go. :)
I don't think it's a good idea to support tag->element mappings without namespaces. The way it works now assures that element classes are associated only with qualified tag names and I think that's the right thing to do.
Stefan