2 ms·
I like that! My own suggestion would be to make :visited something that renders at the browser-chrome level (like OS tooltips or IME controls), rather than the
by derefr 10y ago
I like that!
My own suggestion would be to make :visited something that renders at the browser-chrome level (like OS tooltips or IME controls), rather than the renderer level (like on-page find result highlights or selection-caret link outlines.) Don't hand the state to the renderer process in the first place; just stuff it in the renderer-inaccessible part of the DOM (like XHR response cookies) and then have the browser indicate where on the rendering surface the visited—or maybe unvisited!—links are, in some floating-control fashion (perhaps like Firefox's find-in-page scroll-bar notches.)