The MV3 bugs are stupid ridiculous. Like, I'm gonna open a long-lived communications channel, but it'll be destroyed when the service worker shuts down in an arbitrary n<5 minutes. Okie doke. Clients love to hear it.
The comments on that bug are depressing as well. I generally am involved in much more niche development communities - is this kind of disrespectful back and forth the standard these days?
People are kinda bitter about this. You can design around it, but it makes a lot of things way bigger jobs than they should be. I was just explaining my way around this one today. You port from v2 to v3 and all of a sudden it's basically a rewrite to make everything datum serializable and every function re-entrant because you never know when chrome is going kill your process.
At this point, it's just the way it is now with Google. They promised Crostini for kaby lake chromebooks (I think; maybe another chip) for like 3 years in a row. A thousand comments on there. People are just frustrated.
Oh, I understand the bitterness around Manifest and a lot of it is justifiable.
I was referring to the two developers (both seemingly not Google/Chromium affiliated) arguing about a workaround involving an “injectable tab” and taking pot shots at one another’s comprehension and ability.
https://bugs.chromium.org/p/chromium/issues/detail?id=115225...