| Browser.execute() [message #462664] |
Mon, 17 October 2005 10:48  |
Eclipse User |
|
|
|
Originally posted by: kent.generatescape.com
I am trying to get the browser to execute some javascript.
It returns true, but the browser does not show the effects of the script. I
tried playing with refresh and redraw, but that also didn't work. I tested
the script and it works. Is there something else I have to do to get it
work?
Also, I presume "<!--" and "-->" are not to be passed in as part of the
script, no?
|
|
|
| Re: Browser.execute() [message #462665 is a reply to message #462664] |
Mon, 17 October 2005 10:00  |
 Benjamin Pasero
Messages: 337
Registered: July 2009 |
Senior Member |
|
|
Sometimes it makes a difference wether you are passing in multiple JS commands
into a single execute method, or calling execute more than once, splitting the
commands.
What did you try to execute and on which OS? For instance, JS that triggers
dialogs, like window.print, does not yet work on Mac.
Ben
> I am trying to get the browser to execute some javascript.
>
> It returns true, but the browser does not show the effects of the script. I
> tried playing with refresh and redraw, but that also didn't work. I tested
> the script and it works. Is there something else I have to do to get it
> work?
>
> Also, I presume "<!--" and "-->" are not to be passed in as part of the
> script, no?
>
>
|
|
|
| Re: Browser.execute() [message #462666 is a reply to message #462665] |
Mon, 17 October 2005 10:01 |
Benjamin Pasero
Messages: 337
Registered: July 2009 |
Senior Member |
|
|
"JS that triggers dialogs, like window.print, does not yet work on Mac."
This is to be read as "window.print is not yet working on Mac". Other
Dialogs work as far as I know.
Ben
>
> Sometimes it makes a difference wether you are passing in multiple JS
> commands
> into a single execute method, or calling execute more than once,
> splitting the
> commands.
>
> What did you try to execute and on which OS? For instance, JS that triggers
> dialogs, like window.print, does not yet work on Mac.
>
> Ben
>
>> I am trying to get the browser to execute some javascript.
>>
>> It returns true, but the browser does not show the effects of the
>> script. I
>> tried playing with refresh and redraw, but that also didn't work. I
>> tested
>> the script and it works. Is there something else I have to do to get
>> it work?
>>
>> Also, I presume "<!--" and "-->" are not to be passed in as part of
>> the script, no?
>>
>>
|
|
|
| Re: Browser.execute() [message #462692 is a reply to message #462666] |
Mon, 17 October 2005 13:09 |
| Eclipse User |
|
|
|
Originally posted by: kent.generatescape.com
I just found a solution. I was trying to get highlight.js (this is a part of
the help system) to work on an arbitrary webpage.
However I figured it out. I was using setText, and then execute. Which was
unnecessary. But that might mean that setText & execute don't work together.
So it works, but I sometimes get that annoying javascript error, ha ha, I
have to figure that one out.
thanks.
darn I just replied to the rcp thread about this on accident.
"Benjamin Pasero" <bpasero@rssowl.org> wrote in message
news:divsqq$sr0$2@news.eclipse.org...
> "JS that triggers dialogs, like window.print, does not yet work on Mac."
>
> This is to be read as "window.print is not yet working on Mac". Other
> Dialogs work as far as I know.
>
> Ben
>
>>
>> Sometimes it makes a difference wether you are passing in multiple JS
>> commands
>> into a single execute method, or calling execute more than once,
>> splitting the
>> commands.
>>
>> What did you try to execute and on which OS? For instance, JS that
>> triggers
>> dialogs, like window.print, does not yet work on Mac.
>>
>> Ben
>>
>>> I am trying to get the browser to execute some javascript.
>>>
>>> It returns true, but the browser does not show the effects of the
>>> script. I
>>> tried playing with refresh and redraw, but that also didn't work. I
>>> tested
>>> the script and it works. Is there something else I have to do to get it
>>> work?
>>>
>>> Also, I presume "<!--" and "-->" are not to be passed in as part of the
>>> script, no?
>>>
>>>
|
|
|
Powered by
FUDForum. Page generated in 0.02001 seconds
] 
Search
Help
Register
Login
Home
