I dunno know if this is IE bug or not but suppose you want to insert more nodes into nodes which belong to iframeDom using functions like appendChild and insertBefore.
In that case you should not do node.appendChild(document.createTextNode());
This will fail as document.createTextNode belongs to main document and not iframe document. Instead what you need to do is
node.appendChild(node.ownerDocument.createTextNode());
Friday, December 21, 2007
Wednesday, November 14, 2007
VML Rendering
After loads of pains, I have finally decided to get myself blogging about IE. I always thought I was too lazy to get into blogging but the amount of help I have recently got from bloggers regarding IE pains have made me start this new blog.
The first pain which I will describe is with regards to Vectoir Graphics on IE. I still do not understand why MS does not want to make the life of fellow coders easy. VML is a lost markup language wth almost zero documentation and trust me when I say their documentation sucks big time in MSDN as well. I had to literally spend 2 days to get started with some complex structures on VML and on SVG it hardly took me 3 hours. But this is where the story starts. After that I had to spend almost 5 days to get my entire thing working with VML which I know for sure was 5 days wasted as MS could have easily adopted SVG by now and made our lifes easier. But well enough of MS thrashing (maybe).
Here is the first pain.
I found that when using textpath for rendering texts the text were not appearing properly. The were hardly readable even though I had not scaled them down. I looked on Google and this seemed like a known problem and hence I decided to almost give up. However I decided to give one shot and change my font and walla it worked. First times new roman was my default font and it suked. Then i changed the font to Arial just to give it a trry and to my surprise it improved and then came the idea. Well MS makes their products best suited for their technology as always. Hence I decided to change the font to MS Sans Serif and it looked so wonderful that it almost made me cry with joy. Well I remeber seeing a survey which did say that MS Sans Serif is installed on 99+% browsers so I am happy but probably I would have been happier if it worked as nicely for Times New Roman.
The first pain which I will describe is with regards to Vectoir Graphics on IE. I still do not understand why MS does not want to make the life of fellow coders easy. VML is a lost markup language wth almost zero documentation and trust me when I say their documentation sucks big time in MSDN as well. I had to literally spend 2 days to get started with some complex structures on VML and on SVG it hardly took me 3 hours. But this is where the story starts. After that I had to spend almost 5 days to get my entire thing working with VML which I know for sure was 5 days wasted as MS could have easily adopted SVG by now and made our lifes easier. But well enough of MS thrashing (maybe).
Here is the first pain.
I found that when using textpath for rendering texts the text were not appearing properly. The were hardly readable even though I had not scaled them down. I looked on Google and this seemed like a known problem and hence I decided to almost give up. However I decided to give one shot and change my font and walla it worked. First times new roman was my default font and it suked. Then i changed the font to Arial just to give it a trry and to my surprise it improved and then came the idea. Well MS makes their products best suited for their technology as always. Hence I decided to change the font to MS Sans Serif and it looked so wonderful that it almost made me cry with joy. Well I remeber seeing a survey which did say that MS Sans Serif is installed on 99+% browsers so I am happy but probably I would have been happier if it worked as nicely for Times New Roman.
Subscribe to:
Comments (Atom)