Saturday, January 26, 2008
so, like, i re-do all of this code & stuff & finally, finally get shit working to the point where i can look at specific usage issues, and i find two three issues:
- a number of my .xsl's use msxml extensions
- ie can allow cross-domain access, but ff cannot
- handling of xml data islands in ff
at this point it looks like my cross-browser transform.htc is working just fine. even managed to improve it substantially, although some - interesting - quirks remain. added tracing, error handling; revamped the logic; refactored the implementation.
one thing i've never worked out is how to tell what is calling an event handler when multiple objects share the same handler. i created some work-around for this. i don't really expect "window.event" or "this" to give me what i need, but i still need to check. i'm sure i looked into this multiple times over the years, but nothing came up.
it's the first of the two three items that is the big question mark. dealing with those extensions, with exslt or some such, will be a problem. basically, i use some string & date handling, but exslt support among browsers seems scant to non-existent. do i need to fork my .xsl's ? seems to be the case.
the cross-domain access stuff can be handled with server-side xml proxies. think page scraping with no interpretation needed. what the hell, not too difficult, but two-stepping this shit through my own server seems silly.
still working on that last item. ff is doing some strange things to the dom structure there.
i'm really thinking i should revert to server-side handling of these transforms, obsoleting all the work i've just completed. and i've got some code i did a couple years ago for this. but that wasn't the purpose behind this exercise.
there was a purpose, wasn't there ?
anyway, as this particular behavior is the coronerstone (heh) of my website, i think i'll stop here and ponder. there's no point in doing the rest of these if this one won't work out the way i want.