Jump to content
We apologize for the inconvenience, but chat support is currently unavailable. Please feel free to submit an email ticket or reach out at discussion.evernote.com. Thank you for understanding. ×


Employee Alumni
  • Content Count

  • Joined

  • Last visited

Community Reputation

16 Neutral

About tkaraszewski

  1. My guess is that when Safari is opened, the clipper opens the intro page and sets that value. Then, for the rest of the session, the clipper behaviors properly. But when you quit Safari, it fails to save the settings for the session and so the next time you open it, you start from scratch. My first guess would be to check the permissions for wherever Safari stores this data (on my machine, this seems to be ~/Library/Safari/LocalStorage). You could try running the "Verify Disk Permissions" and "Repair Disk Permissions" tools in Disk Utility and see if this makes a difference. You could also try deleting everything in ~/Library/Safari or ~/Library/Safari/LocalStorage and see if that will reset everything for you (it would also reset all your *other* Safari settings as well, so you may or may not want to try it). That's where I'd start.
  2. The clipper saves a setting in localStorage. If you enable the Develop menu, then open the Clipper window and right-click on it and select "inspect element" (you'll need to restart Safari after enabling the Develop menu to get this option) , you'll get the inspector for the extension. If you click the little icon in the top left that looks like a stack of disks, you'll be able to look through everything that's in localStorage for the extension. There should be a value there called "introShown". If that value is present (and set to 'true') then the Clipper won't show the intro page. If there's something preventing you from saving localStorage data, or another extension (maybe Ghostery?) is clearing it, it you're clearing it out yourself (clearing your cache may do this), then the extension loses all its settings and runs again as if it were installed for the first time.
  3. The fix for this in Safari has been made and it is currently in testing. It will be available in the next release, which should be out soon.
  4. Hey guys, I created a shared note showing how to do this with the Safari Web Clipper extension (Chrome and Firefox should be similar). Please check out the following link: https://www.evernote.com/shard/s151/sh/74f5bc77-fc4a-49a7-8ebb-b70e8a1c1517/8bbd0c697414f5a02caa99a56c503ee5
  5. For what it's worth, I find this behavior annoying too. I use 1Password to manage passwords and wish I could make it work seamlessly with the browser extensions, but the browsers (Chrome and Safari at least, I don't do much work with Firefox, so I'd have to check there) automatically close the extension window when you click away, and there's nothing we can do about it. We made usernames persist in Chrome/Safari, largely because that will let you copy/paste just your password into the extension without losing your username. Firefox will get this behavior too in an upcoming version.
  6. That entire site is a giant iframe, and the Chrome clipper does not support iframes.
  7. To disable the suggestions, click "Options" in the bottom left corner of the Clipper window, and then set "Enable Smart Filing" to "Disable Smart Filing". To hide related notes, click "Hide Related Notes" in the bottom left corner of that window, and they will stay hidden for any future clips until you show them again. To hide this entire window always, go to the Options page by clicking the link at the bottom left corner of the clipper window, and uncheck the "Enable Notifications" checkbox (you will no longer see confirmation that your clips have succeeded). You can also dismiss the Related Notes window by clicking the "Close" button, OR by clicking anywhere outside the window on the page, OR by pressing ESC. -Tyler Karaszewski, clipper dev.
  8. Is this an old version of Chrome? Try updating to the latest Chrome version.
  9. As of 5.6, the Chrome extension uses manifest version 2 as described here: http://developer.chrome.com/extensions/manifestVersion.html Correspondingly, it now uses "background scripts" instead of a "background page" as per here: http://developer.chrome.com/extensions/background_pages.html If you're using a Chromium variant that doesn't yet support these features, then the extension won't work.
  10. Google adds and removes features in Chrome so often that if you're not on the latest version you can find things stop working fairly quickly. Almost every Chrome Clipper release has some change in it that's just meant to keep it working properly in the newest version of Chrome.
  11. I've done some work on this to make the clipping experience better on Twitter. For example, if you look at this tweet: https://twitter.com/tkaraszewski/status/229742856561115137, it will look like this (at least for me): And after doing some work to improve how it clips, the default clip from this page looks like: This change is currently slated to be released in Chrome Clipper 5.7, and should show up in the next Safari release after that as well.
  12. The Safari Clipper is intended to display that welcome page exactly once, and once it does, it stores a setting saying that it has been shown so that it won't appear again. If your regular ritual is to delete all your saved data every time you close your browser, then you are probably deleting this setting and so the Clipper will think that it hasn't displayed the welcome page and show it again next time it starts.
  13. I looked at this. It's weird that it happens at all, but I've just checked in a fix for it, which will go out with the next Safari Clipper release.
  • Create New...