Swizec Teller - a geek with a hatswizec.com

    BrowserStack – a less painful way to test weird browsers

    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.

    Swizec Teller published ServerlessHandbook.dev avatarSwizec Teller published ServerlessHandbook.dev@Swizec
    Client: Hey can you make it work on Edge?

    and here I was thinking I could go to bed early tonight
    Tweet media

    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

    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!

    Swizec Teller published ServerlessHandbook.dev avatarSwizec Teller published ServerlessHandbook.dev@Swizec
    Oh also on Edge node.getBoundingClientRect() doesn't return a DOMRect. Oh no, it returns a ClientRect.

    Unlike DOMRect, ClientRect (which exists only on Edge) doesn't have x and y coordinates. Only top and left


    .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 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.



    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

    Did you enjoy this article?

    Published on March 20th, 2019 in Front End, Technical

    Learned something new?
    Want to become an expert?

    Here's how it works 👇

    Leave your email and I'll send you thoughtfully written emails every week about React, JavaScript, and your career. Lessons learned over 20 years in the industry working with companies ranging from tiny startups to Fortune5 behemoths.

    Join Swizec's Newsletter

    And get thoughtful letters 💌 on mindsets, tactics, and technical skills for your career. Real lessons from building production software. No bullshit.

    "Man, love your simple writing! Yours is the only newsletter I open and only blog that I give a fuck to read & scroll till the end. And wow always take away lessons with me. Inspiring! And very relatable. 👌"

    ~ Ashish Kumar

    Join over 14,000 engineers just like you already improving their careers with my letters, workshops, courses, and talks. ✌️

    Have a burning question that you think I can answer? I don't have all of the answers, but I have some! Hit me up on twitter or book a 30min ama for in-depth help.

    Ready to Stop copy pasting D3 examples and create data visualizations of your own?  Learn how to build scalable dataviz components your whole team can understand with React for Data Visualization

    Curious about Serverless and the modern backend? Check out Serverless Handbook, modern backend for the frontend engineer.

    Ready to learn how it all fits together and build a modern webapp from scratch? Learn how to launch a webapp and make your first 💰 on the side with ServerlessReact.Dev

    Want to brush up on your modern JavaScript syntax? Check out my interactive cheatsheet: es6cheatsheet.com

    By the way, just in case no one has told you it yet today: I love and appreciate you for who you are ❤️

    Created by Swizec with ❤️