Consumer facing stuff so nobody in my use case is running much other than a few versions of Safari or Chrome on desktop or really Safari on mobile. (87-92% iOS on mobile)

Yeah sure but this is tool for internal use

Agree, it's a debugging tool for what users see, and users see your app on WebKit in Safari.

So agree, the PdM should not be using Chrome.

I suggested the Kagi Orion path elsewhere in this comment page too, since that would give the PdM extensions, while still seeing what users see.

Man. It will literally never stop being funny to me when people try guilt-tripping developers into adding Safari support. It's the exact same shtick, every single time:

"Can we have Firefox support? It would really help promote the Open Web."

"Sure, it was on our roadmap already."

"AKTLY You need to rewrite your app for Safari support and WebKit coverage because if you ignore that then imagine how bad the iOS experience will be!!! People will blame you instead of themselves because they're simply too domesticated to fix technology issues, so do their work for them!"

...rinse and repeat for everything Apple refuses to support themselves. We wouldn't be begging people for Safari support if it was a successful browser or if people actually cared about it in the first place.

Millions of people use Safari all day every day.

Developers might not like it but people use it. Personally I use it for almost everything now.

But with a fork of WebKit? I don’t think another fork is all that helpful in the context of trying to fix a bug.

It's not a fork of WebKit. It uses WebKit.

https://blog.kagi.com/orion-features

https://blog.kagi.com/orion-new-features

Ahhh.

Someone said Safari fork but not WebKit fork.

https://news.ycombinator.com/item?id=40323838