When was the last time you had to make sure your app works on weird browsers like Microsoft Edge?

Me, I had to do it earlier this week. My experience building websites for a web agency back in high school meant I knew what I was getting into.


Microsoft Edge did not disappoint.

Array.flat() doesn’t work on Edge. On every other browser it flattens nested arrays. On Edge it blows up and says the method doesn’t exist.

CanIuse for Array.flat
CanIuse for Array.flat

Okay not every browser. Only the ones that people use.

You can solve that with a polyfill right? An npm package that loads itself up and makes Array.flat work.

Yep, makes the error go away. Doesn’t behave the way it does on other browsers. ๐Ÿคฆโ€โ™‚๏ธ

So I had to replace every .flat() with my own hack like this: .reduce((arr, vals) => [...arr, ...vals], []). Sigh

In this project I was also using chroma-js to manipulate colors. Convenient way to take a color and give it a little alpha channel with chroma(color).alpha(0.5).

Except on Edge this created invalid hex values. Colors no work at all.

Had to hack it together like this `rgba(${chroma(color).alpha(0.5).rgba().join(',')})

๐Ÿคจ

You thought that was bad? It gets even better!

.getBoundingClientRect() doesn’t work on Edge. Well it does but it returns a ClientRect instead of a DOMRect. They work the same except when they don’t.

For example DOMRect has x and y coordinates. ClientRect only has top and left. Oh and ClientRect only exists on Edge. Of course.

This meant I had to fix my useDimensions library. Project relies on it a lot to measure stuff and build responsive data visualizations.

Oh and flexbox doesn’t work correctly. Instead of spacing evenly it bunches everything on the left. Of course.


The hero in this story is BrowserStack

Despite all this pain, there is a silver lining ๐Ÿ‘‰ BrowserStack made testing on Microsoft Edge absolutely painless.

Well the testing itself was painful and the results made me cry but I could test.

I’m a Mac kind of guy you see. I don’t have Edge. I don’t have a Windows machine. I have zero interest in VirtualBox and futzing around with images and installing Windows on a partition and whatever else it used to take to test on weird browsers.

With BrowserStack I was able to run Edge in a Chrome tab. That’s right. A Chrome tab emulated an entire operating system running a full screen browser.

Edge probably runs on their servers and streams an image to the tab. Still, feels like magic.

BrowserStack open screen
BrowserStack open screen

BrowserStack really does support all browsers ๐Ÿ‘Œ

You can use it for free for 15 minutes I think. I needed more so I ponied up a whopping $19 for a freelancer plan. That gave me 100 minutes.


You can even run things from localhost. No idea how they made that work. Type http://localhost:3000 into the URL bar and it actually goes to your localhost.

Just don’t type localhost:3000 because Edge doesn’t know how to deal with that and says it can’t reach the URL. ๐Ÿคฆโ€โ™‚๏ธ

And here’s proof. Edge running inside Chrome showing my homepage.


Amazing.

Lucky for us Microsoft is replacing the Edge browser engine with Chrome some time soon. Maybe then we won’t need this anymore ๐Ÿคž

Cheers,
~Swizec

Learned something new? Want to improve your skills?

Join over 10,000 engineers just like you already improving their skills!

Here's how it works ๐Ÿ‘‡

Leave your email and I'll send you an Interactive Modern JavaScript Cheatsheet ๐Ÿ“–right away. After that you'll get thoughtfully written emails every week about React, JavaScript, and your career. Lessons learned over my 20 years in the industry working with companies ranging from tiny startups to Fortune5 behemoths.

PS: You should also follow me on twitter ๐Ÿ‘‰ here.
It's where I go to shoot the shit about programming.