Hi Tom. On Thu, 15 Dec 2011 10:27:33 -0700, Tom Prince <tom.prince@ualberta.net> wrote: > On Thu, 15 Dec 2011 08:14:08 -0400, David Bremner <david@tethera.net> wrote: > > On Mon, 4 Jul 2011 05:59:03 +0400, Dmitry Kurochkin <dmitry.kurochkin@gmail.com> wrote: > > > Result: nothing happens except for "No URL at point" message > > > > > > Expected result: the second message is shown/hidden > > > > Unfortunately this patch is unreliable, reporting BROKEN for some > > environments and FIXED for others; I think you mentioned it depends > > on whether w3m-el is installed? I have reverted it for now to reduce the > > noise in the test logs. > > Would a proper fix for this be to explicitly select which html renderer > is used, and then test it with each renderer in turn? If it is the > renderer that is causing the BROKEN/FIXED distinction, this would > trigger all possbile behaviors. > I know that the issue affects w3m-el renderer and does not affect w3m-standalone. Though it may affect other renderers as well. So we could explicitly set the renderer to w3m-el for the test. But we need to make sure we skip the test if w3m-el is not available. The bug itself is related to keymap property that is set for the rendered HTML. It is set for the final newline as well. And it is rear-sticky. I am not sure about how to better fix this. I do not plan to work on this issue in the near future, so I do not want to spend time on fixing this test case now. If you feel like working on it, you are welcome. Regards, Dmitry > Tom