Bug 188122

Summary:	[Browser] completed event not fired following a backward
Product:	[Eclipse Project] Platform	Reporter:	Antoine Robert <tibetoine>
Component:	SWT	Assignee:	Grant Gayed <grant_gayed>
Status:	NEW ---	QA Contact:
Severity:	major
Priority:	P3
Version:	3.3
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Antoine Robert

2007-05-21 12:05:41 EDT

(Also See Bug : 187282)

Actually, no event is fired for frameset using a page from a different domain, following a backward.

Comment 1 Nitin Dahyabhai

2007-05-21 12:12:44 EDT


*** This bug has been marked as a duplicate of bug 188121 ***

Comment 2 Antoine Robert

2007-05-21 12:31:19 EDT

This bug should not be marked as DUPLICATE since the other one should be delated (It's a mistake).

Thanks

Comment 3 Antoine Robert

2007-05-21 12:34:07 EDT

File informations to reproduce:

Page 1 : frameset.html
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
<html>
	<head></head>
	
	<frameset cols="*,*,*">
		<frame name="f1" src="frame1.htm" />
		<frame name="f2" src="frame21.htm" />
		<frame name="f3" src="http://www.google.fr/" />
	</frameset>
</html>


Page 2 : Local frame 1
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
<html>
	<head>
		<title>Frame 1</title>
	</head>
<body>
	<ul>
		<li>
			<a onclick="parent.frames['f2'].window.location = 'frame21.htm';" href="#">Frame : frame21.htm</a>
		</li>
		<li>
			<a onclick="parent.frames['f2'].window.location = 'frame22.htm';" href="#">Frame : frame22.htm</a>
		</li>
	</ul>
</body>
</html>


Page 3 : Local frame 2.1
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
<html>
	<head>
		<title>Frame 21</title>
	</head>
	<body>
		<p> Frame n° <b>1</b> </p>
	</body>
</html>


Page 4 : Local frame 2.2
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
<html>
	<head>
		<title>Frame 2</title>
	</head>
	<body>
		<p> Frame n° <b>2</b> </p>
	</body>
</html>

Comment 4 Eclipse Webmaster

2019-09-06 15:31:11 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.