Mozilla , xml, xsl, css and Javascript. — OZONE Asylum, home of the Mad Scientists

XML - XSL - XSLT - XHTML - CSS - DOM

Mozilla , xml, xsl, css and Javascript.

This page's ID: 21814

Edit Post

Who can edit a post?	The poster and administrators may edit a post. The poster can only edit it for a short while after the initial post.

Your User Name:
Your Password:
Login Options:	Remember Me On This Computer

Your Text: Insert Slimies » Insert UBB Code » Close Last Tag \| All Tags UBB Help	Ok, it's all about a simple project involving a xml/xsl solution. I cannot publish the file on the web: they're copyrighted by my school, and therefore authorities of the state where I live. It sounds silly for such a project, but I tend to dislike spreading stuff I don't own, eventhough I am the author. Anyway, here is my problem: the xml is well formatted, using the standard compliant method to link to an xsl stylesheet: [code] <?xml version="1.0"?> <?xml-stylesheet type="text/xsl" href="main.xsl"?> [/code] The xsl is well formatted, using two namespaces: the standard xsl namespace, and an xhtml namespace. Also, I am rendering the transformed result as html (output method == html). IE parses the whole correctly. The final page is linked to a css and a js file, for extra features. As I said, IE parses the whole perfectly, or almost perfectly (some event related functions behave oddly depending on what triggers them), Mozilla parses the whole perfectly too. But does not RENDER the whole perfectly: many glitches appear, mainly when playing with the css display. As a static document, it would be perfect. The dyn features cause some oddities though, mainly the fact the display isn't adjusted correctly, lags... What I am trying to figure out is: is Mozilla really messing up with "linking elements at runtime" (css+xsl+xml+js = much stuff), or am I doing something wrong? Oh, in the js part, I use snippets like the following to toggle the display of a [tr] on/off. [code] function hideAll(){ // fonction qui affiche le contenu des tr dans un élément coll=document.getElementsByTagName("tr"); // saisit la collection "tr" de l'objet courant for(i=0;i<coll.length;i++){ // parcourt la collection en question if(coll[i].className!=="alwaysVisible"){ // si le tr courant n'a pas "alwaysVisible" comme attribut "class" coll[i].style.display="none"; // on met l'attribut css "display" à "none" coll[i].style.visibility="hidden"; } } } [/code] I then use "display: text;" to make the tr visible again. It "almost" works in Moz too, but oddly: the element which should be hidden is, at times, the only one remaining visible, and mouseover events tend to produce unwanted spaces. etc.. Oh, I almost forgot to ask a targetted question: - does anybody have experience with xsl on Mozilla? Possibly with js in addition? - am I doing something wrong with the display property? Could I use it better? Or affecting the tr maybe... should target something else? [small](Edited by [internallink=947]InI[/internallink] on 05-16-2004 19:36)[/small] Loading...
Options:	Enable Slimies Enable Linkwords

« Backwards — Onwards »

Show Forum Drop Down Menu