Navigation

Search

Categories

On this page

Awesomeness, in a box.
Rendering difference between Firefox and IE when using innerHTML

Archive

Blogroll

Disclaimer
The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.

RSS 2.0 | Atom 1.0 | CDF

Send mail to the author(s) E-mail

Total Posts: 25
This Year: 0
This Month: 0
This Week: 0
Comments: 5

Sign In
Pick a theme:

 Saturday, August 23, 2008
Saturday, August 23, 2008 1:06:00 AM (GMT Standard Time, UTC+00:00) ( Microsoft Internship | MVC )
Well, its been a fun summer, but my time at Microsoft is over ...


... for now :).  It looks like I'll be coming back full-time come next August, so it's a bittersweet end.  I'll miss the people on my team and the interns I've met, but in most cases I'll see them again next year!  Keep an eye on this blog, because you can bet I'll be posting when the stuff I worked on goes live!

Comments [0] | | # 
 Tuesday, August 19, 2008
Tuesday, August 19, 2008 5:30:23 PM (GMT Standard Time, UTC+00:00) ( Microsoft Internship | Random Stuff )

Thanks to Alex Tuteur for typing up the lyrics from our scribbles on paper, to Kyle Farnung for filiming, converting and posting the video, to Kristine Johnson for singing the epic win-ness, and to all the people who helped write the song!

STILL AROUND
By Andrew Nurse, Kristine Johnson, Alex Tuteur, Ben Butler, Kyle Farnung, Steven Truong (EXP), Adam Kiu, and William Hong

Internz: a triumph
I’m sending a lolcat: EPIC FAIL
It’s hard to understate procrastination
MICROSOFT INTERNS
We do nothing but read mail all day
For the good of all of us
Except for the FTEs
But there’s no sense crying over broken compiles
You just keep on building, it’ll work in awhile
And the coding gets done
And you make a bad pun
For the interns who are
STILL AROUND

I’m not really working
I’m reading Internz all day long
Even though I didn’t meet commitments
And now it’s review time
And it is my future on the line
As I leave it sucks because
I was so happy right here
Now it’s time to leave and I am packing my bag
To go back to my school and deal with the jet lag
So I’m GLaD that I’ve turned
Think of all the cash we’ve earned
As the interns who are
STILL AROUND

I’m going to leave now
I guess you prefer to stay right here
Maybe I’ll find someone else to work for
Maybe at Google
THAT WAS A JOKE, HAHA, FAT CHANCE
Anyway this lolcat’s great
It’s so amusing and fun
Look at me still coding when there’s packing to do
When I look out there it makes me GLaD I’m not you
I’ve got all my boxes done
Now it’s time for me to run
Bye bye interns who are
STILL AROUND

I can’t believe you are all
STILL AROUND
I’m done with coding and you’re
STILL AROUND
I’m leaving now and you are
STILL AROUND
While I’m at school you’ll be
STILL AROUND
And when I’m back here you’ll be
STILL AROUND
STILL AROUND
STILL AROUND
Comments [3] | | # 
 Saturday, August 16, 2008
Saturday, August 16, 2008 12:54:35 AM (GMT Standard Time, UTC+00:00) ( JavaScript | Microsoft Internship )
I know, its been a while since I've blogged, but I'm just so busy with my Microsoft internship its been hard to find time. Anyway, on to the post...

I've been doing quite a bit of JavaScript work recently and I discovered an interesting inconsistency between Firefox and IE when it comes to the innerHTML project. Federico, from the ASP.Net QA team blog, posted the details on that blog, but here's a quick summary.

Basically, it comes down to when the browsers perform whitespace normalization. In HTML, multiple whitespace (space, tab, newline etc.) characters are treated as a single space. Also, whitespace at the beginning of "block" elements (which are elements like DIV which have newlines before them) is removed. In Firefox, the whitespace is preserved exactly as typed when stored in Firefox's internal structures. When the HTML is rendered out, Firefox performs the normalization on the fly. However, in IE, the whitespace is normalized before the internal structures are built.

The result of this is that the contents of the innerHTML property for a DOM element can vary between these two browsers.

Check out the blog post for more details.

Comments [0] | | # 

Search with Google

Google