Tags

I’m looking for a device I can use for WebKit/Safari testing. However, I can’t justify splashing too much cash on a Mac that I’ll scarcely use.

I’m looking at something with Apple Silicon so that it won’t be dropped by the next software update. Currently considering a 2020 M1 MacBook Air with a broken screen, which I can use headless. Maybe a Mac Mini, but they’re pretty scarce on the second-hand market. People seem to hang onto iMacs long-term, so they aren’t really around.

Thinking the Neo down the line, perhaps.

Any thoughts?

Sometimes you find yourself deep in the decaying bowels of the archived Safari HTML Reference and you’ve just got to look at yourself and ask ‘Where did I go wrong?’

I’m excited for the MacBook Neo from the perspective of it being a reasonably priced Safari/WebKit testing machine.

I imagine they’ll be cheap second-hand as well due to the education market.

The lower-end specs shouldn’t be an issue for testing either. They might even prove a benefit.

Haven’t got an Apple device but need to test your site in Safari? Go into the Apple Store and test on their demo computers.

They probably won’t kick you out. It usually takes them a while to catch on.

I find it very odd when people refer to ‘two main browser engines’, those being Gecko and WebKit.

Do people really think Blink hasn’t diverged significantly enough to consider it another engine at this point?

I found it interesting that WebKit maintains a collection of ‘quirks’ – hardcoded, website-specific fixes and tweaks.

https://github.com/WebKit/WebKit/blob/main/Source/WebCore/page/Quirks.cpp

The phrase ‘WebKit magic’ is something I could live without.

Hey, err, web devs on Windows. How do you guys test for WebKit?

As far as I can see, not a single native Windows WebKit browser exists…