I mean that could be "two Safari tickets" for all we know, and you could be ignorantly chasing Chrome's ChromeOS un-standards or bleeding edge RFCs thinking a reference implementation or a mere memo should work everywhere. Personally, I almost never see Safari-specific bugs be reported and can't find one in my company's JIRA system in the last year. Are you sure you're not self-inflicting this pain?
Your desire for Safari to vanish is also historically short sighted. Ladybird has near-zero usage, Firefox is practically dead and is fully bought and paid for by Google, everything else is just a Chrome or Chromium fork. Safari is realistically the only thing holding back an outright Chrome monopoly with meaningful usage.
The safari literally broke border-radius of image whenever a opacity transition is triggered. It's the simplest effect you will see everyday. Or broke layer of position: fixed element when containing container is scrolled. They aren't even new features and exists since like 10 year ago? And it's still broken that requires specific workaround. Or on ios 26(the one just released). Every page that added to ios home screen is no longer able to play video at all if you close it and open it the second time. The list can go on infinitely if I ever want to dig up. When is the crap even usable? There isn't a way to not hit bugs at all unless your page is extremely barebone and require little interaction.
Besides these, the service worker debugger never work on my iphone device since like two major version ago.(It did not show up in the safari menu) There is no way to use it as a developer even I want to (let alone the devtool crashes and disconnects frequently)
Your desire for Safari to vanish is also historically short sighted. Ladybird has near-zero usage, Firefox is practically dead and is fully bought and paid for by Google, everything else is just a Chrome or Chromium fork. Safari is realistically the only thing holding back an outright Chrome monopoly with meaningful usage.