| Key: |
WTR-204
|
| Type: |
Bug
|
| Status: |
Open
|
| Priority: |
Major
|
| Assignee: |
Unassigned
|
| Reporter: |
gabriel wilkins
|
| Votes: |
0
|
| Watchers: |
1
|
|
If you were logged in you would be able to see more operations.
|
|
|
Watir
Created: 25/Apr/08 12:19 PM
Updated: 10/Jun/08 02:12 PM
|
|
| Component/s: |
None
|
| Affects Version/s: |
1.5.4
|
| Fix Version/s: |
1.6.2
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
Environment:
|
winxpsp2, rb186, wtr154
|
|
to reproduce:
*in irb:*
ie = Watir::IE.new
ie.maximize
ie.minimize #controls the cmd window, and not IE.
probably related to http://jira.openqa.org/browse/WTR-179 but considerably more practical with no obvious workaround.
for instance, if you have merb kicking off a rake task, it seems to be the same issue. it seems to be merb catching the min/max, because nothing happens to the IE window.
|
|
Description
|
to reproduce:
*in irb:*
ie = Watir::IE.new
ie.maximize
ie.minimize #controls the cmd window, and not IE.
probably related to http://jira.openqa.org/browse/WTR-179 but considerably more practical with no obvious workaround.
for instance, if you have merb kicking off a rake task, it seems to be the same issue. it seems to be merb catching the min/max, because nothing happens to the IE window.
|
Show » |
|
minimize/maximize affect wrong window / don't do anything
backing up to 1.5.3 doesn't fix it.
i could have sworn it used to work, no idea what else to check.