They call it Mozilla

They call it Mozilla. Home to many open source software projects, ranging from Firefox and beyond – and boy does the keyword ‘open’ ever so stand out.

Having worked three days at Mozilla (building K) is surreal. As mentioned on the wiki, I have been ‘splashed’ with the Mozilla hose! From bewilderment to clarity and astonishment to excitement, my last three days can relate to a unique roller coaster ride.

Mozilla is unlike any office I have envisioned or have worked in before. From the surprisingly large bottom floor open area with the sectional couches, lawn chairs, bean bag chairs and projector screen to the open area conference rooms and work stations, Mozilla truly understands what being open is all about. The openness and split from the ‘norm’ definitely brings forth a true sense of comfort. When I sit on the large sectional couches, I cant help but envision sitting in a friend’s basement and I understand why – it brings about the most interesting ideas, discussions and topics.

The people I have met so far are all truly passionate about their work and it definitely shows when the opportunity arises through weekly meetings. Having attended three meetings, I have heard the thoughts of many unique individuals speak passionately about the work they do. Of the three, from platform discussion to weekly QA to last Monday’s ‘all hands’, each a one-of-a-kind event.

They call it Mozilla because they are about openness and difference and it demonstrates – they really are a workplace like no other. I am happy to contribute through my internship this summer.

On a more technical note, I am working on writing tests for bugs that bring forth rendering issues in the layout engine caused by invalidation. The type of tests are considered reference tests or reftests. They traditionally work by taking a snapshot of the entire window at the end of the test and comparing that to a snapshot of the reference page.

However, there’s a fairly large class of bugs classified as “invalidation bugs” — they only show up when you redraw part of a page, and when you draw the whole page everything’s fine. This is where the new form testing comes in that I am currently focusing on.

An example of a bug I picked, is bug 449362 – where in the past, simple HTML table borders have been rendered incorrectly when table cell sizes changes due as a result of running JavaScript.

Only three days in and lots more to come so stay tuned – I know at least one is waiting 🙂


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: