Version: (using KDE 4.3.1) OS: Linux Installed from: Ubuntu Packages This is javascript error that effectivelly prevents use of konqueror with a number of interactive sites. When toString() method is applied to the functions that are HTML element event handlers, returning value is incorrect, it doesn't contain function's "{}" (braces) around the function body. For example, if we set attribute onload of the page body element to "window.alert(this.onload.toString());", it results in: function onload(event) window.alert(this.onload.toString()); while expected value is: function onload(event) { window.alert(this.onload.toString()); }
May be my description was not so clear. Here it is with a more detailed example. If an HTML document has <body> element and onload event handler set on it via "onload" attribute like following: <body onload="window.alert(this.onload.toString())"> this document, when loaded, shows popup message containing toString function result like this: function onload(event) window.alert(this.onload.toString()) while the expected value should include function body braces and should look like this: function onload(event) { window.alert(this.onload.toString()); } Some sites use event handler chaining technique consisting of the converting present handler to string, then contcatenating this string with another one that contains chaining code, and then assigning as event handler function with eval of the result of concatenation. Something like this (snipped may not work, only as illustration): function chainSomethingToOnload(element, something) { var handler = ""; if (element.onload) { handler = "(" + element.onload.toString() + ").apply(this, arguments);" } handler += something; element.onload = function () { eval(handler); }; } With the error described this technique doesn't work at all throwing exception at the time when eval tries to parse combined handler body. Sites using this technique are fully unsable with konqueror.
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!