shadowmoses

I have a bit of a workaround for those interested. In my case, this worked with trying to capture Washington Post comments. Let's say the goal would be to capture all currently visible comments. What I did was: Highlight any portion of text starting from the first comment. Continue to hold down the mouse/left-click. Hit the "End" key on your keyboard. This should bring you down to roughly the end of the comments section. Extend the highlighted section a little bit in order to ensure the last comment would be completely highlighted (you can let go of the mouse/left-click at this point). Right-click on any section of the highlighted text, then select "Print". Save as PDF. It's obviously not an ideal solution nor an elegant one, but at least it works without too much fuss. I'm going to test this method with some other websites I frequent in order to determine if it could potentially represent a more generalized solution rather than for a select few use cases.

For notes created in-house, I understand that this sort of action could be accomplished through the duplication of user-created "Template" notes with pre-existing tags. However, for content brought in via the Web Clipper, such functionality would be entirely missing. For instance, I may want to apply different sets of tags to incoming clipped content depending on the source, content type, etc. Although the web clipper does allow specific tags to be applied to all clipped content, this would not represent a sufficient solution. If we could utilize our own named tag sets via the Web Clipper, this issue would be instantly resolved. As of right now, the only alternatives would be to apply tags one by one or to handle content from within Evernote, neither of which would be ideal when applying several or more tags.

I would also like a solution to this, as the same issue applies to Washington Post comments.

I understand the at-best skeptical and at-worst irritated reaction to this self-proclaimed and entirely vague refreshing. However, I can also understand the thinking behind such a refreshing effort despite its lack of initial substance. Consider the following two scenarios: -An introduction of several user-requested features along with general performance improvements followed by a rebranding marketing campaign. -An initial rebranding marketing campaign followed by the introduction of several user-requested features along with general performance improvements. If I am Evernote, I would go with Option B over Option A every time. Or, better yet, Option C, where Evernote would have announced this refresh alongside a description of meaningful changes. I guess that would have been asking for too much. /s Without a doubt, we should be highly skeptical of Evernote suddenly doing a 180 with regard to long-standing performance and functionality issues, but maybe this truly is the start of a change in priorities. The combination of this announced refresh, a few high-level executives leaving the company and the aforementioned glaring issues which, I would suspect, have impacted Evernote's bottom line give me at least some hope of them having finally seen the light. With that said, there remains the risk Evernote will instead make the choice to put fluff innovation first before core functionality, which will only alienate us moderate-to-heavy users even further. Just how important we are to Evernote compared to new and/or casual users remains to be seen, but we should find out soon enough. I won't be holding my breath obviously, but I'm willing to give Evernote a bit of time to show us something. If they are truly serious about this rebranding effort, they should follow up with something of substance soon. If nothing comes of it, I think it's safe to say Evernote will never put reliability first.

Thanks a bunch for this, it worked perfectly for me. I would suggest others follow this workaround in the meantime.

Normally I might be more understanding of a slow response to this issue if it were buried amongst other, more pressing requests or if we represented a very small minority (unlikely, though not impossible) but considering that this is the highest upvoted thread under "Web Product Feedback" coupled with the complete silence on EN's end, I have to say I'm quite disappointed in this instance. Not enough to do anything drastic or whine incessantly, but disappointed nonetheless. You would think a "fix" for this would be quite easy to implement as well.