Bug 73623

Summary:	Add TargetFrameName to browser.LocationEvent
Product:	[Eclipse Project] Platform	Reporter:	Mike Hoeffner <mikehoeffner>
Component:	SWT	Assignee:	Grant Gayed <grant_gayed>
Status:	NEW ---	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	carolynmacleod4, Michal.Tkacz
Version:	3.0
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Mike Hoeffner

2004-09-09 17:29:42 EDT

Please consider adding a TargetFrameName variable to browser.LocationEvent. 
This can be set when a BeforeNavigate2 event is handled in browser.Browser with
code along the lines of:

newEvent.targetFrameName = event.arguments[3].getString();

It might also make sense to provide access to the other event data (Flags,
PostData, and Headers) as listed at:

http://msdn.microsoft.com/library/default.asp?url=/workshop/browser/webbrowser/reference/events/beforenavigate2.asp

An issue with adding these fields to LocationEvent is that none of these
additional fields are available on a DocumentComplete event, which also uses
LocationEvent.

Comment 1 Christophe Cornu

2004-09-10 14:16:01 EDT

Mike:
In which situation do you need the targetFrameName info for?

Comment 2 Bernhard Fastenrath

2005-12-31 15:43:00 EST

The name of the target frame can be relevant when an existing document with frames (e.g. a javadoc) is enclosed in a larger document structure. The "_top" frame of the javadoc is suddenly a subframe and indistinguishable from frames inside the javadoc.
I have exactly that problems with http://dolphin.sourceforge.net/book/, where I enclose an arbitrary document (which may have subframes) in an iframe controlled by the application (the book reader). When this iframe is used the application can no longer distinguish changes of the document top frame from changes to other frames.

I noticed, by the way, that the event.top flag is always false, even when the top frame changes.
(SuSE Linux 9.1, Mozilla 1.7.3)

Comment 3 Eclipse Webmaster

2019-09-06 16:15:10 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.