If I'm understanding this, the root issue is NOT with the disabled button, but is with the text field that should enable the button, (once the text field is filled in).
There may be a fire event attached to that text field which is NOT being met when you run with Celerity. As I understand it Celerity is a headless browser, so as the test works with Watir using the IE browser, perhaps Celerity doesn't cause the expected fire event to automatically occur when the text is entered into the text field. In which case you may need to explicitly raise it. Check your JS code for that text field to see if it expects an event (i.e. "onMouseOver", "onClick", etc.), and then use the Watir::Element class fire_event method to send that event. Joe On May 18, 4:26 am, Eugene Pirogov <[email protected]> wrote: > Well yeah, you're right. Sorry for a confusing "manual" word. > > Ok. The point is — I'm porting a Watir test to Celerity. The case is simple > — once a textfield is filled with arbitrary text, button is activated > automatically via JS. Watir actually acts as intended — it activates the > button; but in Celerity the button somehow keeps staying disabled (I guess > that's a celerity issue to investigate). > > On Tue, May 18, 2010 at 1:15 PM, Željko Filipin < > -- Before posting, please read http://watir.com/support. In short: search before you ask, be nice. You received this message because you are subscribed to http://groups.google.com/group/watir-general To post: [email protected] To unsubscribe: [email protected]
