You get to decide yourself how good of a job to do on your bug reports, so I don’t see where the problem is. If it bothers you that it takes work and you can’t see everything that Apple sees, just let those of us who don’t mind a bit of typing effort take care of it.
>If it bothers you that it takes work and you can’t see everything that Apple sees, just let those of us who don’t mind a bit of typing effort take care of it.
I completely agree, which is why I was just pointing out that the "it only takes a few minutes" is technically true, but a little misleading as nobody is going to be able to write a good bug report, create an apple account, report the bug, have it most likely get closed as a dupe, request access to the dupe, get access to the dupe, subscribe to the issue and wait for it to be fixed and released in "a few minutes".
Whereas making a polyfill could realistically happen in 30 minutes or so, and publishing it to NPM if you feel like it maybe another 10 if you are familiar with the process. And I don't feel like people should be criticized for not wanting to jump through Apple's hoops to report a bug and have it get fixed upstream when the alternative is not only faster, easier, and more public, but also can get deployed to your users right now.
