The following are the minimum conditions for the bug to occur:

1. The page must be a frame in a frameset
2. The frame must have a name set in the HTML of the frame defenition:
   <frame name="framename" src="frame.html">
3. JavaScript must be used by the page to 'rename' itself to the same name as specified in the HTML (the bug will not occur if you rename it to a different name):
   window.name = 'framename';
         or
   window.name = window.name;

Safari 1.1.1 (v100.1) and above (tested 1.2 [v125] also) will incorrectly mangle the name to something completely wrong:
<!--framePath //<!--frame1-->-->

Earlier versions of Safari (including 1.0) do not have this problem and no other browser has this problem.