To be able to quickly find a post and insert a link.
While it works at first, over time, this bogs down considerably. Also, the search results aren't great - users have to scroll down a bit to find posts that should have matched well. One user suggest prioritizing title matches since that's what many folks are searching for.
Multiple browsers: switching to another browser helps temporarily, as does clearing local data. But over time it slows down again no matter the browser.
http://www.screencast.com/t/Sqq5S0t5AAu via one of our users
This was brought up in our forums & we've been trying to spot the bug for a while. I couldn't reproduce it, but Timmy tried it on en.blog and was able to get it after a while.
+1 I've experienced this a lot on internal P2 sites.
Reported in #301030-hc as well.
Experiencing this on my personal site (cate.blog) and also on internal p2s. Would also say that in general Calypso is feeling a bit laggy but shows up very noticeably when trying to add links. Happy to provide a video or run some kind of profiling tool if that would be helpful.
@catehstn if you could, and wouldn't mind, testing out the same flow with linking in https://calypso.live/?branch=fix/editor/12481 and let us know if it feels faster there? Thanks!
Hey! Tried it and feels faster. Thanks!
Thanks for testing @catehstn !
Just checking in on this - is there anything else we need to do to make it go?
Thanks for the nudge @supernovia - looks like the branch in #12528 needs some attention, I will try to update that today and find someone to give it the final 馃憤
Re-opening based on a report by @catehstn that the wplink experience is still very slow and laggy for her -- specifically on internal Automattic P2 (the mobile team's "Hogwarts" site).
A bit of anecdotal feedback:
Takes ages to load, unresponsive
can't select my post so ended up finding the link and pasting it over.
my general impression of that component is that it ranges between "unusable" and "meh". It's never snappy.
First load is slowest, second load is faster but still unusable.
My bet is a JS Wrangler doing some benchmarking could find the bottleneck and a fix.
See also https://github.com/Automattic/wp-calypso/pull/12528 as the last time the code was improved, CC @timmyc