troggy

Just to add that I've been having this issue for a while now, also on latest android but with pixel 3a. I found advice on other app problems on this forum to clear the app cache and storage and reinstall the app. Perhaps it will work for you. I did that months ago, it fixed things for a few hours then the old problems described by Uknotes recurred. Over time I've been though this clear and reinstall process twice, but still it persists (or to be more precise - returns after a short time). I've since stopped setting tags on mobile and having to rework them in web. Or often just not getting around to tagging at all. So I'm now working on an alternative to evernote using zim on desktop (with keep notes as an optional bridge from mobile to desktop). This might not suit most users but will work for me - and give me assurance that I hold the content for the future. Who knows what evernote will do tomorrow!? As to evernote itslef, well today I reinstalled the app (again) and it worked ok at first but quickly I see it saved one item twice over, which is another annoyance. I've read elsewhere that evernote's legacy code is so convoluted they have a job to get it working well. I expect the product will eventually come right but my guess is it may be some more years yet! I hope the tags will keep working well now, but not holding my breath!

Just recently Web clipper has been working much more gracefully with Google Chrome's privacy settings. Certainly now on version 100.0.4896.127 (Official Build) (64-bit). Don't know if it's improvements in the Chrome browser or in the Evernote web clipper extension, but hopefully that's the end of this thread now.

Like I said, please stay on topic please

I feel pinkelephant's comment is a bit off topic. It's more about how one approaches security, whereas this thread is simply about clipper not working with security features in the browser. Some users might not care for the browser feature, but others who do find the way clipper doesn't play well with it a problem.

Clipper is still behaving badly here [Version 89.0.4389.114 (Official Build) (64-bit) on Debian 10] - I just tested it and it made the browser start to flash like mad. No obvious way to stop this flashing, I had to close the browser and restart it, then turn off the option again. In case it helps other users, my temporary work around is to allow the clipper full access but then not allow it in incognito mode: and remember to use incognito for things like bank websites so anyone exploiting clipper can't spy if they try.

Sorry if my original post was not clear enough. Let me try again. When I right click on the clipper icon in Google chrome, a context menu opens up. I then select the option that says "this can read and change site data" and three more options appear: "When you click the extension" on the current domain "on all sites" So while clipper is designed to run on all sites, google chrome can restrict it so it only runs in a narrower range of pages. This is presumably intended to protect the user's privacy by giving control over when an app (like clipper) can 'see' the page content and when it can't . I have selected the first option "when you click the extension". With that setting chosen I expect to then be able to use the clipper icon to clip a selected page. In this case when I click the clipper icon I get prompted to reload the page. this makes sense since the clipper hasn't been able to see the page so far. What should happen I think, is that when the page is reloaded Chrome should give clipper access to it. But nothing useful happens after I reload. If I click the clipper icon after the reload, the same instruction to reload the page appears once more, and so on. If I set the third option instead "on all sites", then clipper works as it should, but that way I have given clipper permission to access all pages I visit, even when I have no intention of clipping those pages. In short, the privacy option that Google have provided is interfering with how clipper developers expect it to work, with the result that users can set options that make clipper appear broken. I'm guessing that probably clipper was designed before Google provided this new privacy option. Now that the privacy option is there, I would think clipper could be modified to work with his new feature. My bug report is intended to make developers aware that there is an issue. Obviously it is up to the developers whether they want to accommodate it, but I think they ought to care to do so. It doesn't look good on evernote that they aren't keeping an eye on things and testing in the developing real world environment.

Chrome version Version 83.0.4103.61 (Official Build) (64-bit) on debian buster Google chrome provides extension permission control so the web clipper either runs all the time on all sites, or only when clicked, or on selected domains. Clipper works when it has permission to all sites, but if I choose "only when clicked", it doesn't work and plugin options become unavailable. I do get a notice that a page refresh is required for it to run, but it then still doesn't work.