[Webtest] [dev] How to specify the browser to simulate for js support

[Marc Guillemot]

Dierk Koenig wrote:
> a sidemark:
> 
> I noticed the nested <option> tags are not longer processed but
> still possible to set. We should remove setOption() from the
> config then.

the problem I had with this option tags was that they allowed "direct" configuration of HttpUnit options. I would have 
been quite tedious to look for all what was possible (and perhaps absolutely not used) and make the new version do the 
same. I think too that will shoud remove setOption().

> How do we process options in the future?

Option that are recognized are really interesting should have named attributes. I start in a separate email a poll to 
see what is used.

> What about e.g. enabling/disabling JavaScript processing?
> Any ideas?

For JS processing I see two issue:
- an option to disable JS for a step sequence would be interessant.
- a step to disable/enable JS within a test sequence could be usefull as well. It would permit to disable js before 
getting a page that contains not supported js and to reactivate it on the next page. The option for the sequence would 
not be necessary if we have the step.

Marc.