Vincent

Thanks for reporting! Since this is an extension issue, I'll move it to the extension project. And in case it's helpful as a temporary workaround, note that you can disable...

I've just encountered this in v1.30.0. Looking at my stack trace, and comparing that to [the fix in #1942](https://github.com/inrupt/solid-client-js/pull/1942/files), I don't think that that `try..catch` block was added to the...

Confirming that it appears to be resolved for me, thank you!

@eramdam I expect that [our workaround](https://github.com/mozilla/fx-private-relay/pull/2612/commits/e26f79a85f2fe11ba08408cac7d8e8c50b9e23ce#diff-edbffc39ec80534abfe406392e700ab7da225db46156fe9898a7ad34675b5e50) should work there as well, but passing the menu trigger state instead of the overlay trigger state. @brandonpittman I don't think that the existence...

Thank you @janbrasna, that is correct!

@joshuadegier The icon button has to be reachable via the keyboard to assist some users with motor or visual impairments, who otherwise would not be able to reach it. However,...

Thanks @czlucius, I actually have a prototype working with exactly that approach*, and it does appear to work well so far. Unfortunately it does require some more work to get...

Not much I think, unfortunately. The main thing is that the team needs to review and get familiar with the refactored codebase so they can build on top of it,...

@balessan Ah, looking at your code, it seems to me that instead of storing a token on a `headers` property, you could have your constructor take a `fetch` function instead,...

I just encountered this issue in SCAB (so browser, not Node) version 1.11.7. I didn't open a new issue since this one was still open. Might this have regressed again?