8817 2006-05-09 18:04:50 -0700 REGRESSION: TinyMCE: Clicking on a link has no effect 2006-07-18 16:23:34 -0700 1 1 1 Unclassified WebKit HTML Editing 420+ Mac OS X 10.4 RESOLVED INVALID http://tinymce.moxiecode.com/example.php?example=true InRadar, Regression P1 Normal --- 7156 1 justin.garcia webkit-unassigned ian oldest_to_newest 41659 0 justin.garcia 2006-05-09 18:04:50 -0700 When you hover over a link inside the editable region, the href that appears in the status bar is correct, but when you click on the link nothing happens and the status bar text changes to Run script: "void(0);" We think this is a regression in TinyMCE's sources. 41809 1 timothy 2006-05-09 21:57:28 -0700 This might not be a regression in TinyMCE but an intentional change to prevent bug 7156. This might install an click handler that calls void(0) to prevent the navigation. It is hard to say by looking their whitespace-stripped script file. 44849 2 alice.barraclough 2006-06-06 07:52:48 -0700 <rdar://problem/4575096> 50031 3 darin 2006-07-16 06:23:16 -0700 (In reply to comment #1) > It is hard to say by looking their whitespace-stripped script file. Full source to TinyMCE is at their website, so someone should look at that and verify that this is intentional on their part. 50306 4 dacarson 2006-07-18 16:09:05 -0700 Both Opera 9.0 and FF 1.5.0.4 exhibit similar behaviour. Clicking the link does nothing. FF and Safari ToT does allow you to right click the link and open in new window/new tab, which opens the link to sourceforge. Checking the code, it seems that the experience behaviour is correct. Here is the code that handles link selection in MCE: // Patch the darned link if (lnk && e.type == "mousedown") { lnk.setAttribute("mce_real_href", lnk.getAttribute("href")); lnk.setAttribute("href", "javascript:void(0);"); } // Patch back if (lnk && e.type == "click") { window.setTimeout(function() { lnk.setAttribute("href", lnk.getAttribute("mce_real_href")); lnk.removeAttribute("mce_real_href"); }, 10); } As can be seen, javascript:void(0) is correct. 50310 5 dacarson 2006-07-18 16:23:34 -0700 Not a bug