Most web pages cause an unhandled promise rejection within the LastPass Safari extension. We have a global "unhandledrejection" handler installed, so it sees that unhandled rejection and shows a "something went wrong" page. How do we ignore errors like this from extensions?
-
Show this thread
-
This isn't a problem with reporting to BugSnag etc. It's just `window.addEventListener("unhandledrejection", ...)`, and LastPass' extension is broken so we see their error.
2 replies 1 retweet 6 likesShow this thread -
LastPass' extension breaks on most web pages right now. So either: 1. everyone uses an error filtering mechanism that I can't seem to find via google, or 2. LastPass users can't use the web at all, or 3. no one actually uses `window.addEventListener("unhandledrejection", ...)`?
5 replies 1 retweet 9 likesShow this thread -
Replying to @sgrif @garybernhardt
Actually you only mentioned Safari, so there's option 4: LastPass users overwhelmingly use Chrome (which I guess implies option 2 for Safari)
3:21 PM - 7 Aug 2019
0 replies
0 retweets
0 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.