From konq-bugs Thu Sep 02 17:15:38 2004 From: Thomas Friedrichsmeier Date: Thu, 02 Sep 2004 17:15:38 +0000 To: konq-bugs Subject: [Bug 65606] handling of target "_new" in window.open Message-Id: <20040902171538.7621.qmail () ktown ! kde ! org> X-MARC-Message: https://marc.info/?l=konq-bugs&m=109414534300105 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. http://bugs.kde.org/show_bug.cgi?id=65606 ------- Additional Comments From thomas.friedrichsmeier ruhr-uni-bochum de 2004-09-02 19:15 ------- > This bug is wrong but a part of it is right. I will explain this :) This is right, but a part of this is wrong ;-) Three points: 1) On target "_new" You'll note, that in the origingal report I was not sure, whether "_new" was a legal target-name. I know by now that it is not. However, a quick search on google will show you that I am not the only one confused about this: http://www.google.com/search?hl=de&ie=ISO-8859-1&q=target%3D%22_new%22&btnG=Suche&lr= Actually, in my personal opinion, this is good enough a reason to bend the standards a bit and treat "_new" just like "_blank". After all, few web-developers will chose target="_new" when they actually don't want a new window. I.e. the harm done if konqueror would bend the standards here is very little, while there is a non-zero cost to strict interpretation of the standards. Well, this is my personal opinion, and if others think, konqueror should be strict on all standards, I can see the merit of that, too. 2) Illegal target names like "_foobar" or "1thing" The standard says, those should be ignored entirely, konqueror (now) treats them just like any legal non-special target-name. Personally, once again, I think this behavior is reasonable. I can see no merit in adhering to the standard, which in this case would - as far as I understand it - ask to open the link-target in the current frame/window. Once again, that's just my opinion. 3) The original bug report ... ... was about an inconsistent handling of link-targets with plain HTML vs. JavaScript. that issue seems to be resolved as of konqueror 3.3. The testcase from comment #6 seems to work fine as well (except for issues 1) and 2)). So actually this bug could/should be closed. I'm not closing it myself right now, in case you think 1) or 2) are still an issue to be dealt with. _______________________________________________ Konq-bugs mailing list Konq-bugs@mail.kde.org https://mail.kde.org/mailman/listinfo/konq-bugs