Closed jkjelsbak closed 10 years ago
Hey there. I've just released a new update, which refactors a lot of the code. Please give 1.1 a go, and let me know if you continue to experience trouble.
Checking back in to see if the last update has fixed the issue for you. Please advise.
Sorry for loosing attention - today I did test with version 1.1.
From the console :
[blocked] The page at 'https://xxxxxxx.com/browse/xxxxxx' was loaded over HTTPS, but ran insecure content from 'omnifocus:///add?name=%5Bxxxxxxxxx%5D%20%22Items%20left%22%20field…ged.%20%0A%0ASee%20enclosure.%20%0A%20%20%20%20%20%20%20%20%20%20%20%20%0A': this content should also be loaded over HTTPS.
As fare as I can see the Chrome (Version 31.0.1650.57) ruling can be changed by clicking the shield icon which appearing at the end of the address bar. This will allow Chrome to load insecure content
Thanks for our effort…...
Thanks for the update.
Someone's actually filed a report for this in issue #4 — I hope to take a look at this over the weekend. I also appreciate for the workaround tip for the "blocked" issue, I'll post it to that thread.
Published fix with v1.1.1 update to Chrome Web Store.
I have used this nice feature previously, but for some reason it doesn't work any longer.