Browser execute function in child window [message #465212] |
Thu, 08 December 2005 04:07  |
Eclipse User |
|
|
|
I have good results from using Browser.execute as a means
to communicate with the embedded browser instance [Windows/IE],
but I am not doing so well in attempting to do the same with
a pop-up from the embedded instance. I would appreciate either
of these types of help:
a. Examples of successful invocation of anything like:
browser.execute ("someFunction();");
where someFunction, at some point does: childWindow = window.open();
browser.execute ("childWindow.someFunction();");
b. Advice on debug/trace method that might help in determining where
the breakdown occurs. IE, as you know, doesn't give me any decent
debug assistance as would Firefox, and hours of trying everything I
can think of has not resulted in any progress.
Thank you.
|
|
|
|
|
Re: Browser execute function in child window [message #465390 is a reply to message #465363] |
Mon, 12 December 2005 10:09  |
Eclipse User |
|
|
|
You should enter a feature request for this against Eclipse Platform SWT.
"Terry Corbet" <tcorbet@ix.netcom.com> wrote in message
news:299d9dd8590d69f72a12da4204117ae1$1@www.eclipse.org...
> Veronika,
>
> Thank you. I know I can do what you suggest, but the
> result is not truly the same as there would not then be
> any communication between the parent and the child, unless
> I 'wired' that through the Browser status event mechanism.
>
> While your work-around is quite reasonable, should my
> problem be submitted as a bug to be worked on? I believe
> that the Browser OLE implementation has either an
> incompatibility or an outright defect. Whether your answer
> to my question is 'yes' or 'no', if you can give me any
> guidance on how to trace/debug the failure, I want to see
> if I can help define what is broken. It would really be
> desirable to have a single Browser instance that could
> pop-up children as required AND for the rich client to be
> able to communicate with the script engine in that child
> with the same facility that we can now communicate with the
> script engine in the parent.
>
> Thank you.
>
|
|
|
Powered by
FUDForum. Page generated in 0.08998 seconds