MantisBT - NetSurf |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0002430 | NetSurf | Javascript | public | 2016-02-21 15:54 | 2016-03-07 13:37 |
|
| Reporter | Chris Young | |
|---|
| Assigned To | | |
|---|
| Priority | normal | Severity | minor | Reproducibility | always |
|---|
| Status | acknowledged | Resolution | open | |
|---|
| Platform | Amiga | OS | AmigaOS | OS Version | 4.1 |
|---|
| Product Version | 3.4 | |
|---|
| Target Version | | Fixed in Version | | |
|---|
| Fixed in CI build # | |
|---|
| Reported in CI build # | 3421 |
|---|
| URL of problem page | http://www.unsatisfactorysoftware.co.uk/netsurf/onclick.html |
|---|
|
| Summary | 0002430: onClick in 'a' tag is ignored |
|---|
| Description | Whilst onClick appears to be working for buttons, in 'a' tags the attribute is ignored. |
|---|
| Steps To Reproduce | Visit http://www.unsatisfactorysoftware.co.uk/netsurf/onclick.html
Click on the link, which should redirect to the NetSurf homepage.
(I'm not sure if that Javascript works in NetSurf, but there is nothing in the log to suggest it is even firing the event)
|
|---|
| Additional Information | The code is:
#
It is my understanding that the onclick should execute, and if it doesn't return false then the usual href kicks in.
|
|---|
| Tags | No tags attached. |
|---|
| Relationships | |
| Attached Files |  ns.log (92,347) 2016-02-21 15:54
https://bugs.netsurf-browser.org/mantis/file_download.php?file_id=414&type=bug |
|---|
|
Notes |
|
|
|
Curious. The source of the cited URL is tiny. When I open the page and click repeatedly on the link, the throubber does something briefly each time - NS is doing something. The log say "Dispatching 'click' against"... but nowhere in the log does the target URL (netsurf-browser.org) appear. Surely it should appear, at least once, somewhere in the log?
Are we just reloading the page instead of visiting the target? |
|
|
|
|
|
It's not Amiga-specific - my observations in my note above are from RISC OS with CI #3421. |
|
|
|
|
I think it's following the href and not running the onclick code.
The log does say it is dispatching the click but doesn't then go on to say "Hooray! An event!". So it looks like it isn't registering the onclick from the tag as an event, from the limited amount I understand about this stuff.
It could well be "not yet implemented". |
|