Issue Details (XML | Word | Printable)

Key: WTR-6
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Bret Pettichord
Reporter: Bret Pettichord
Votes: 0
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
Watir

click_no_wait only works with IE, not other container objects.

Created: 10/Mar/06 04:36 PM   Updated: 03/Jun/08 10:46 PM   Resolved: 19/Sep/06 01:32 AM
Component/s: Modal Web Dialog
Affects Version/s: 1.5.0/1.5.1
Fix Version/s: 1.5.0/1.5.1

Issue Links:
Relationship
 


 Description  « Hide

To be useful, the following usages must be supported:

objects in ie, objects in frames, objects in dialogs.

We still need to add frame support.

ie.frame("foo").button(:value, "foo").click_no_wait



Sort Order: Ascending order - Click to sort in descending order
David Schmidt added a comment - 15/May/06 11:49 AM

Fixed in modal_dialog Branch by adding Container#to_identifier method to create an element string to recreate the current object and by adding the :hwnd method to IE#attach_to_browser to guarantee that a no_wait option is applied to the correct parent IE instance.


Bret Pettichord added a comment - 15/May/06 09:48 PM

David has a fix for this in the modal_dialog branch


Bret Pettichord added a comment - 15/Jun/06 12:16 PM

click_no_wait works in IE and ModalDialog.

To make it work in Frames, we need to provide Frame#attach_command.

That will make it work everywhere.


Bret Pettichord added a comment - 19/Sep/06 01:28 AM

duplicate


Bret Pettichord added a comment - 19/Sep/06 01:32 AM

Completed with commit 1095