htmlunit-user

[Htmlunit-user] RE: How to disable ECMA-Errors in the JavaScript engine

[Klaus-Peter B. <Kla...@we...>]

Hi Chris,

unfortenately, this is little help provided by the htmlunit developer guys ;-(
I know that there is the setJavaScriptEnabled(false) feature, but sometimes I NEED JS execution!
E.g., my code does not work because the <DIV ...> statement is not processed properly, or another piece of code does not work because Window.setInterval() is missing.

So I decided to go the hard way and patch the code by myself!
In the case of the <DIV...> statement I have already succeeded to write a workaround, and setInterval() is on the way...
Seems that is what open source is all about...

--Klaus
_________________________________________________________
Mit WEB.DE FreePhone? mit hochster Qualitat ab 0 Ct./Min.
weltweit telefonieren! http://freephone.web.de/?mc=021201

Re: [Htmlunit-user] RE: How to disable ECMA-Errors in the JavaScript engine

[<ddk...@ki...>]

Stubbing out support for the "setInterval()" method would also fix some
of the tests that hit various CNN web sites in the SanityCheck test
class.  (The JavaScript actually appears in banner ads for those sites!)

I thought someone already uploaded a patch for this, but I can't find
any relevent Bugs, Patches or RFEs on the SourceForge project site.

Dave


On Sun, Sep 19, 2004 at 08:13:04PM +0200, Klaus-Peter Berg wrote:

> Hi Chris,
> 
> unfortenately, this is little help provided by the htmlunit developer guys ;-(
> I know that there is the setJavaScriptEnabled(false) feature, but sometimes I NEED JS execution!
> E.g., my code does not work because the <DIV ...> statement is not processed properly, or another piece of code does not work because Window.setInterval() is missing.
> 
> So I decided to go the hard way and patch the code by myself!
> In the case of the <DIV...> statement I have already succeeded to write a workaround, and setInterval() is on the way...
> Seems that is what open source is all about...
> 
> --Klaus

Re: [Htmlunit-user] RE: How to disable ECMA-Errors in the JavaScript engine

[Your G. <yo...@br...>]

Sorry for the delay; had an email server crash and lost a few messages so this is
the first I saw :( 

There was a patch for setInterval() submitted a long-long time ago but it wouldn't
apply and left a thread running so it was rejected. 

If you have a patch that in any way makes things better than they are please post it
to the patch tracker and I'll get it applied ASAP. This will get it into the nightly
build and I'm hoping to do a release of some sort next week if our fearless leader
doesn't beat me to it :p (I'm in the process of moving right now so time is
limited).

What's this <DIV...> problem??

Brad C

--- "David D. Kilzer" <ddk...@ki...> wrote:

> Stubbing out support for the "setInterval()" method would also fix some
> of the tests that hit various CNN web sites in the SanityCheck test
> class.  (The JavaScript actually appears in banner ads for those sites!)
> 
> I thought someone already uploaded a patch for this, but I can't find
> any relevent Bugs, Patches or RFEs on the SourceForge project site.
> 
> Dave
> 
> 
> On Sun, Sep 19, 2004 at 08:13:04PM +0200, Klaus-Peter Berg wrote:
> 
> > Hi Chris,
> > 
> > unfortenately, this is little help provided by the htmlunit developer guys ;-(
> > I know that there is the setJavaScriptEnabled(false) feature, but sometimes I
> NEED JS execution!
> > E.g., my code does not work because the <DIV ...> statement is not processed
> properly, or another piece of code does not work because Window.setInterval() is
> missing.
> > 
> > So I decided to go the hard way and patch the code by myself!
> > In the case of the <DIV...> statement I have already succeeded to write a
> workaround, and setInterval() is on the way...
> > Seems that is what open source is all about...
> > 
> > --Klaus