Live data from Hacker News

Cannot read clipboard from service worker in a MV3 chrome extension (2020)

bugs.chromium.org

31–40 of 56 posts

Re: Cannot read clipboard from service worker in a MV3 chrome extension (2020)

#31

> Thanks for the issue.... > Thanks..... Aside: Do people know that trailing "..." tends to communicate annoyance or sarcasm? I think the people writing it think it means something else, like some sort of intermission before the next thing they write, but I wouldn't include it in professional comms at all.

> tends to

Online communication styles might be more diverse than you assume.

If something you receive feels stylistically out of place to you, you’ll get more value (and less frustration) by expanding your own dictionary rather than prescribing a narrower one to the author.

Re: Cannot read clipboard from service worker in a MV3 chrome extension (2020)

#32
post #24

Earlier quoted context omitted.

Do you also apply this logic to all other forms of hardware and software? For example TVs that spy on what you're watching.

When I install any piece of software I assume it could do anything and everything on the system.

I don't think most people operate under this assumption, or do not reckon with this.

Re: Cannot read clipboard from service worker in a MV3 chrome extension (2020)

#33
It's extremely frustrating how some chrome extension apis such as chrome.tabCapture simply are no longer background context compatible, since they aren't in service workers. And they're just completely silent, don't even acknowledge the shortcomings. Just a hugely frustrating developer experience. Shame on Google, and this whole MV3 fiasco has permanently soured my view on Chrome developer Relations.

Re: Cannot read clipboard from service worker in a MV3 chrome extension (2020)

#34
My company had a chrome extension they used for making twilio phone calls. V3's service worker focus made that a complete nonstarter. Ended up writing a thing to make phone calls in a background tab, use the Broadcast channel Api to communicate between the background tab and the active tab, and wrote instructions on the background tab for allowing sound permissions explicitly. The plus side is that we likely won't be dependent on chrome anymore, but I expect I'm not at the only company who got a rude awakening from the v3 transition. And yes, you can use v2 extensions with chrome enterprise, which I have no interest in doing.

Re: Cannot read clipboard from service worker in a MV3 chrome extension (2020)

#35
post #21

Earlier quoted context omitted.

I think it has a different tone to different people? I had a friend who used to put it after most messages and I thought they were upset with me until I asked. It was just how they wrote. I've also noticed more people using it to indicate a trailing off of voice, not necessarily with any annoyance emotion.

Maybe it’s a cultural thing cause even a trailing voice does communicates the same connotations of being upset. I know of only two buses of the triple dots: showing there’s more content in a quote or to express annoyance.

Some people use it to let an expression breathe a bit, modifying a period to be more like a paragraph break, or a paragraph break to be even a bit wider.

In some cases, that may represent emphasis, and might take it as an invitation to think on what was said because it was especially earnest or important.

In other cases, it might just a cleanser between ideas that don’t have a clear bridge.

Re: Cannot read clipboard from service worker in a MV3 chrome extension (2020)

#37
post #18

I know there are a lot of valid complaints about Manifest v3, but I don't understand this one. You're telling me that browser extensions should be able to read and write to my clipboard silently at all times, with no user activation or notification? Honestly, that's kind of horrifying, and I'm shocked to hear it existed on v2 extensions. It sounds like a great way to build a keylogger for user passwords. What are som…

More than 10 years ago I built a Firefox extension that was using the clipboard. It was for Multilanguage users that accidentally type in the wrong language, once they notice they type in the wrong language, they clicked a button/hot-key, and the text would switch to an alternate language in their OS. I was eventually in the process of switching it to a Windows app, so it could also work outside the browser, but neve…

Sounds like a punto switcher tool

Re: Cannot read clipboard from service worker in a MV3 chrome extension (2020)

#38

It's extremely frustrating how some chrome extension apis such as chrome.tabCapture simply are no longer background context compatible, since they aren't in service workers. And they're just completely silent, don't even acknowledge the shortcomings. Just a hugely frustrating developer experience. Shame on Google, and this whole MV3 fiasco has permanently soured my view on Chrome developer Relations.

[deleted]

Re: Cannot read clipboard from service worker in a MV3 chrome extension (2020)

#39
post #23

Earlier quoted context omitted.

No, I don’t think people think that… because that isn’t what it means. People aren’t annoyed or sarcastic towards you… they are just pausing for a second.

I feel as though a comma and the end communicates a pause better. Especially since it use in formal English is similar.

My personal use for trailing ‘…’ is precisely to escape formal language and hint at something that is more complex or emotional than a simple pause.

For instance “Did you just…unplug and replug the machine?”

Re: Cannot read clipboard from service worker in a MV3 chrome extension (2020)

#40

I know there are a lot of valid complaints about Manifest v3, but I don't understand this one. You're telling me that browser extensions should be able to read and write to my clipboard silently at all times, with no user activation or notification? Honestly, that's kind of horrifying, and I'm shocked to hear it existed on v2 extensions. It sounds like a great way to build a keylogger for user passwords. What are som…

What is true is that if you remove all features that chrome extensions can do then you won't have any problem as extensions will be useless.

Are you too going to be shocked that any js analytics tags could record all passwords if they wanted?

Should all extensions be able to read the clipboard? No. Should some be able to? Of course

Post reply on HN