Browsers this works in
Browsers this works in
This is the whole list, and beside each line is the thing that stands behind it. A browser we say we test is one an automated suite drives through the product on every release. A browser we say we expect is one we believe works and have not proved, which is a weaker statement and is written as one.
| Browser | Engine | What we run there |
|---|---|---|
| Chrome on the desktopTested on every release | Blink | Every release, the whole suite |
| The engine most of this was built against. Every board test, every money test and every policy test runs here before anything is merged. | ||
| Edge on the desktopExpected to work, and not in our automated tests yet | Blink | Nothing automated |
| The same engine as Chrome, under another name. We do not run a second suite on it, so it is not on the tested list — and there is nothing in the board that turns on a difference between the two. | ||
| Safari on the desktopTested on every release | WebKit | Every release, the whole suite |
| The engine Safari ships, under the Mac keyboard convention: the board's shortcuts answer to the command key here rather than to control. The whole suite runs on this engine on every release, on the same pinned browser build a developer's machine can start, so what we know about Safari is measured rather than checked by hand. | ||
| Firefox on the desktopTested on every release | Gecko | Every release, the whole suite |
| The one engine in this list that shares no ancestry with the others, which is what makes it worth running. The whole suite runs on it on every release. The one thing it does not draw is the pixel comparison of the mirrored board, which is kept for Chrome's engine and Safari's; every behavioural test runs here. | ||
| Phone browsersNot supported yet | WebKit | Every release, every page outside the board |
| The board itself is not supported on a phone: its selection, wiring and multi-select gestures have no touch equivalent yet, and giving them one is a release of its own. The pages around the board open on a phone, though some are not yet laid out for a small screen. Signing in, the terms, this page, your projects and your account are run on a phone-sized Safari engine on every release, so that much is measured. | ||
What “tested” means here
One thing and nothing else: an automated suite drives the real engine through the product — signing in, agreeing to the terms, drawing a board, spending credits, reading a receipt — and a release is held until it passes. It is not a compatibility badge, and it is not a promise that nothing will ever be wrong on your machine. It is a statement that we look, every time, and that we expect to hear about a break before you do.
Versions
We publish no minimum version, because we do not test against old builds and a number with no test behind it is not a claim. The suite runs the engine builds our pinned test tooling ships, which track the current release of each browser. If a page here looks wrong, updating the browser is the first thing worth trying.