3 ms·
Thanks a lot for this positive reply! I am thrilled to read that this might be counted a regression and actually fixed. I really hope that can happen. Regard
by mlang23 7y ago
Thanks a lot for this positive reply! I am thrilled to read that this might be counted a regression and actually fixed. I really hope that can happen.
Regarding 'L', Lynx sometimes "hides" links if the anchor is around a div. Maybe it is just that simple. IIRC, <a href=...><div>...</div></a> will trigger a similar behaviour.
Regarding your Chrome suggestion, that really doesnt help me much since I spend 99% of my workday on a plain virtual console. The context switch of moving to another computer that runs Windows for simple searches is really not practical.
Again, thanks for spotting this and acting on it!
- mbrukman 7y agoHi Mario, Your analysis is correct; the issue was due to <div> tags appearing inside <a> tags. This should be fixed now; I've verified that I can follow result links using Lynx. Once again, my apologies for you running into this issue! Thank you for reporting & debugging it and thank you for your patience as well. I hope this is resolved for you now; please try it out and let me know whether or not it works for you, or if you run into any other issues.