{"items": [{"author": "lifelonglearner", "source_link": "https://www.lesswrong.com/posts/YoFLDnAmMoFj76HPN#3x7gmBwAk4xwxufZZ", "anchor": "lw-3x7gmBwAk4xwxufZZ", "service": "lw", "text": "Can other people comment about the UX of preview on hover?\n<br><br>I dislike it because the pop-ups are often quite large, like on gwern.net, where they can completely block whatever it is I'm reading. Arbital-style tool-tips and the Wikipedia ones are borderline okay as they aren't too large, but I find that the visual contrast is often too jarring for me :/\n", "timestamp": 1593038007}, {"author": "jefftk", "source_link": "https://www.lesswrong.com/posts/YoFLDnAmMoFj76HPN#DapwnaWCQJAMYYmYH", "anchor": "lw-DapwnaWCQJAMYYmYH", "service": "lw", "text": "&rarr;&nbsp;I set mine up so that the pop-ups wouldn't cover content, putting them in the right margin.  Does that fix the UX for you?\n", "timestamp": 1593042079}, {"author": "lifelonglearner", "source_link": "https://www.lesswrong.com/posts/YoFLDnAmMoFj76HPN#Tiok8YySC2teWympX", "anchor": "lw-Tiok8YySC2teWympX", "service": "lw", "text": "&rarr;&nbsp;&rarr;&nbsp;Yes, having them to the margin is much much better. :)\n", "timestamp": 1593043060}, {"author": "Raemon", "source_link": "https://www.lesswrong.com/posts/YoFLDnAmMoFj76HPN#wdcNq9ijkttdJFExQ", "anchor": "lw-wdcNq9ijkttdJFExQ", "service": "lw", "text": "It seems plausible to me that having hovers Off To The Side may be better than the current thing LW does. I do find that the jefftk.com hovers are... too far off to the side. I'd prefer them if they were basically just to the right of the main column.&nbsp;<br><br>(I also don't really mind them appearing in the main body, perhaps not surprising since I helped implement the LW ones, but it'd make sense to me if other people preferred them to-the-side. I think I generally find it less distracting to have the Right By The Hover when I deliberately moused over them, but if I'm just scrolling quickly it can sometimes be annoying. Though this might be solved by just implementing a slight delay to their appearance)", "timestamp": 1593038778}, {"author": "jefftk", "source_link": "https://www.lesswrong.com/posts/YoFLDnAmMoFj76HPN#qTo9Eo89m7mtHnFoX", "anchor": "lw-qTo9Eo89m7mtHnFoX", "service": "lw", "text": "&rarr;&nbsp;\n<br><br>I do find that the jefftk.com hovers are... too far off to the side. I'd prefer them if they were basically just to the right of the main column.\n\n<br><br>You're right, that's where they should go.  I'll go mess with the CSS.\n", "timestamp": 1593042841}, {"author": "jefftk", "source_link": "https://www.lesswrong.com/posts/YoFLDnAmMoFj76HPN#QTJ8KJa9qnNHNLKQB", "anchor": "lw-QTJ8KJa9qnNHNLKQB", "service": "lw", "text": "&rarr;&nbsp;&rarr;&nbsp;Fixed!\n", "timestamp": 1593045650}, {"author": "Dagon", "source_link": "https://www.lesswrong.com/posts/YoFLDnAmMoFj76HPN#CZTvsrvfRAWkFnFZ2", "anchor": "lw-CZTvsrvfRAWkFnFZ2", "service": "lw", "text": "&rarr;&nbsp;It&apos;s very tricky to make it convenient for most, without losing accessibility for some.  Preferences and device capabilities vary by a whole lot, and unless you&apos;re going to do the work to detect or ask people, and then support multiple mechanisms, you are probably best off being as close to minimal and standard as possible.<br><br>My primary mechanism for reading branching sites/articles (those with multiple topics I want to follow) is to open a lot of tabs, then work forward through them, opening more in the process.  Hover is convenient to give me a quick idea of whether it&apos;s worth opening a tab, but it&apos;s really inconvenient if it stays too long or slows me down when I already know I want the tab.<br><br>LW goes a bit too far toward this, for me.  It&apos;s fine on desktop, where I have lots of screen real-estate and the mouse click/focus works to dismiss the popups/hovers pretty well.  It kind of annoys me when middle-click or control-click don&apos;t work to bring up a new tab (for shortforms or some comment-notice links), but that&apos;s tolerable.   On Chrome on iOS, at least, it&apos;s _very_ annoying.  in order to long-press to get the &quot;open in new tab&quot; option, it brings up a window that obscures a lot of other items, and there&apos;s no obvious way on the small screen to dismiss the &quot;hover&quot; without changing the underlying view in some way.  ", "timestamp": 1593272717}, {"author": "acdw", "source_link": "https://www.lesswrong.com/posts/YoFLDnAmMoFj76HPN#SGXSFTRmaJHgEbPH9", "anchor": "lw-SGXSFTRmaJHgEbPH9", "service": "lw", "text": "On Firefox/Windows, hovering over the link turns it purple, though I haven&apos;t *really* visited it. I&apos;m not sure how to change it or if it matters, but I use the :visited pseudo-class often when browsing the web.", "timestamp": 1593039489}, {"author": "jefftk", "source_link": "https://www.lesswrong.com/posts/YoFLDnAmMoFj76HPN#b9jqyuCqvTF3AJJWZ", "anchor": "lw-b9jqyuCqvTF3AJJWZ", "service": "lw", "text": "&rarr;&nbsp;Weirdly, this isn't permanent: it goes away on refresh.  So this isn't actually adding entries to your visited list?\n", "timestamp": 1593042300}, {"author": "romeostevensit", "source_link": "https://www.lesswrong.com/posts/YoFLDnAmMoFj76HPN#TbyBu9WMbHEhnjp2t", "anchor": "lw-TbyBu9WMbHEhnjp2t", "service": "lw", "text": "I think this is especially great for rapid development of technical jargon in nascent fields.", "timestamp": 1593041171}, {"author": "itaibn0", "source_link": "https://www.lesswrong.com/posts/YoFLDnAmMoFj76HPN#EwcAswZ39G5brEXCX", "anchor": "lw-EwcAswZ39G5brEXCX", "service": "lw", "text": "I don&apos;t like the fact that the preview doesn&apos;t disappear when I stop hovering. I find the preview visually jarring enough that I would prefer to spend most of my reading time without a spurious preview window. At the very least, there should be a way to manually close the preview. Otherwise I would want to avoid hovering over any links and to refresh when I do, which is a bad reading experience.", "timestamp": 1593049811}, {"author": "rmoehn", "source_link": "https://www.lesswrong.com/posts/YoFLDnAmMoFj76HPN#ui6AqC34JhsE99tJ5", "anchor": "lw-ui6AqC34JhsE99tJ5", "service": "lw", "text": "I like it the way it is!", "timestamp": 1593053610}, {"author": "kithpendragon", "source_link": "https://www.lesswrong.com/posts/YoFLDnAmMoFj76HPN#Jf5drzB85exHmvCK5", "anchor": "lw-Jf5drzB85exHmvCK5", "service": "lw", "text": "I don't think it matters that the link preview covers the content because the preview should be where your attention is when you're engaging with that feature. Now that it's fairly standard for the content section to take up the middle ~1/3 of the screen, there's plenty of empty space on both sides where the mouse cursor can be routinely kept out of the way. It's more useful to have the cursor near the scrollbar or browser UI most of the time anyway. In fact, it's optimal to keep the cursor in a set region of the screen when you aren't using it so you always know where it is. Accidentally triggering the preview window can be a useful indicator that the cursor is in the wrong place a sub-optimal resting position.", "timestamp": 1593082156}, {"author": "jefftk", "source_link": "https://www.lesswrong.com/posts/YoFLDnAmMoFj76HPN#kSdLurShtGpCaxXtr", "anchor": "lw-kSdLurShtGpCaxXtr", "service": "lw", "text": "&rarr;&nbsp;\n<br><br>the preview should be where your attention is when you're engaging with that feature\n\n<br><br>I don't want to force users to engage with the feature if they don't want to, or keep their cursors in any particular place.\n", "timestamp": 1593088881}, {"author": "kithpendragon", "source_link": "https://www.lesswrong.com/posts/YoFLDnAmMoFj76HPN#iSf7zibq7Bjyk7qer", "anchor": "lw-iSf7zibq7Bjyk7qer", "service": "lw", "text": "&rarr;&nbsp;&rarr;&nbsp;(nodding) I hear that. One more note: other than using the link text as the title of the preview, I don't see anything visually connecting the preview with the link. This makes the feature substantially less discoverable than the current solution, and it could potentially be confusing to have a seemingly random box suddenly appear on the side of the page for no immediately apparent reason if you accidentally hover over a link.", "timestamp": 1593195417}, {"author": "Zvi", "source_link": "https://www.lesswrong.com/posts/YoFLDnAmMoFj76HPN#7Coymavc9fzPP8x59", "anchor": "lw-7Coymavc9fzPP8x59", "service": "lw", "text": "Do you know a good way to implement a preview function in Wordpress?", "timestamp": 1593087743}, {"author": "jefftk", "source_link": "https://www.lesswrong.com/posts/YoFLDnAmMoFj76HPN#rzhGkqLcC5DDPXFDQ", "anchor": "lw-rzhGkqLcC5DDPXFDQ", "service": "lw", "text": "&rarr;&nbsp;It looks like there used to be a plugin for this? https://wordpress.org/plugins/wp-live-preview-links/ https://github.com/soderlind/wp-live-preview-links ?  But visiting the demo page https://soderlind.no/wp-live-preview-links/ it doesn't seem to work anymore.\n", "timestamp": 1593089073}]}