Can private identifiers be removed from this polyfill to widen browser support? #25
Description
Edit: Since this polyfill makes use of public class fields, and class fields landed in Safari 16, my suggestion to replace private elements with non-private elements is moot. I'll leave this issue open in case the maintainers would like to respond, but I recognize that getting a wider baseline of support isn't as easy as I initially believed.
Thanks for making this polyfill! I'm excited about the developer experience improvements the ariaNotify() API offers for the cases where ARIA live regions are particularly tricky.
The problem
My company's app targets users on Safari >= 13.1. Private identifiers only landed in Safari 14.1 (per CanIUse), which means we have to downlevel this polyfill at build time using Babel. While this is certainly fine, it introduces a ton of code.
The solution(?)
Can the identifiers that are currently private be made public, replacing the #<field> syntax with __<field> for pseudo-privacy? Looking at the source code, I don't quite understand why some things are private. If I'm missing something, please correct me! I'd be happy to make a quick PR for this, if the maintainers would like!