It was so much of a problem that at work we added a check that you were charging from the right ports to our internal doctor script (think like `brew doctor`).
I help out with an emulation community. Any time anyone with a 2019 MBP comes in with issues, I stop them from giving any more details and just have them check this first.
I should've worded differently. By the narrative of this website, Google is "paying" Mozilla & Apple to remove XSLT, thus they are "controlled" by Google.
I personally don't quite believe it's all that black and white, just wanted to point out that the "open web" argument is questionable even if you accept this premise.
> Indeed, while Chrome is displaying the dialog, it blocks all Chrome extension popup windows from appearing.
We discovered this one the hard way at work. I keep learning this the hard way myself because I've been working on browser extension dev lately. I don't understand how this could possibly be an intended feature.
This can be useful for accessibility. For example you might have a colour palette that users can add to, but the colours are only stored as hex codes. Giving a screen reader user just RGB values isn't as helpful as providing a name alongside it.
It was so much of a problem that at work we added a check that you were charging from the right ports to our internal doctor script (think like `brew doctor`).
reply