User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 2.0.50727; .NET CLR 1.1.4322) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051111 Firefox/1.5 This bug is related to 290740 and 295930, but somewhat more bugly. First, specifications state that forward slashes are allowed in GET parameters (ie http://www.somesite.com/page.html?getvar=/some/var/with/slashes). If such a page contains an iframe in designmode, any code dragged into it or pasted from the same site which contains absolute urls will get an incorrect absolute to relative transformation, treating all slashes as if they are part of the real path. In this case, pasting in <a href="http://www.somesite.com/images/image.gif>...</a> will result in <a href="../../../../../images/image.gif">...</a>, an obviously incorrect result, with a '../' for every false and real path member. Whatever code is making this transformation is making a fatal assumption about the meaning of slashes in the current pages complete href. Reproducible: Always Steps to Reproduce: 1.Go to a page with a designmode iframe which also has a get parameter with slashes. 2.Paste or drag in code with an absolute url referring to somewhere on the same site. Actual Results: The slashed get parameter is treated as part of the path. Expected Results: The pasted URL will point to the correct location. As others have stated in the bugs mentioned above, I believe we would be better off not doing this transformation at all, pasting in the URL exactly as given, and relying on the user or his/her editing agent to sort it out. At the very least the transformation should produce the correct result, though.