Vimium - unable to click javascript buttons

[sasank89]

On a web page with a form, the "submit" button has the link -
WebForm_DoPostBackWithOptions(new WebForm_PostBackOptions("ctl00$cphMainBody$lbSubmit", "", true, "", "", false, true))

This gets highlighted by Vimium on pressing the 'f' key. But, it doesn't do any action on using that key. On Vimium 2.1.2, chrome 131.

Tried checking all the online solutions, but unable to find an answer why. Thank you for your help on this.

[philg-dev]

Is there any chance you could link that page? Without further information, it's going to be difficult to analyze the situation properly.

A quick google search brought up that this is something that ASP.NET seems to generate. I'm personally not familiar with that framework, so any additional information you can provide would be helpful.

[philg-dev]

Also a quick test on jsfiddle showed on my end that Vimium is definitely capable of detecting and clicking buttons with onclick=javascript:... even though the usage of javascript: URLs is highly discouraged. So it is definitely not a general problem in that regard.

See MDN about javascript URLs

Tiny JS Fiddle Demo:
https://jsfiddle.net/7p5aL8rz/7/

[sasank89]

Thank you for looking into this so quickly. You are correct in the ASP.NET. The web page ends in .aspx. Unfortunately, the page is behind a login page.

I extracted the HTML code from the page source, the parts which pertain to the elements in question. I have removed some of the copyright text from within it, but the HTML code is otherwise intact. The lines in question are on line 108 and 109. In the rest of the file, there are other similar javascript:WebForm_ links. All of them are not able to be clicked by vimium.

extract_vimium.md

Hope this helps. Please let me know if I can provide any more information. Thank you so much for this extension!

[philg-dev]

Just to clarify: I'm not the Vimium author - I'm just a user trying to help out to my best ability.

Unfortunately I'm kinda at my whit's end with your issue. As I'm not familiar enough with the ASP.NET tech stack and I don't know any sites that use it in the same way as the website in question. As long as I can't easily reproduce the issue, I can't try to debug it efficiently - I'm sorry.

Maybe somebody else is able to help.