…turned was actually the type of element we're looking for. In IE8 the test seemed to pass (maybe multiple calls to getElementById would give you the next one if there were multiples?) but IE9 just returns the first one afaik. So now we simply check that the type of element we got is in the expected list of types for the element. Otherwise we fall back to the standard lookups.
… could correct this for only those elements but it would make for an ugly locator change. Instead I chose to make a name method that looks at the html attribute. This will work for all elements and correct the issue we're seeing in IE9 without corner case logic
… return ''
…type or cut/paste code
… differently so there's no default method
…en and would not highlight the control when you set currentstyle. Further this could cause errors on some pages and raise a js error that the dom is not modifiable. For IE9 we now just use ole_object.style (instead of currentstyle which element#style is aliased to).
…, so it was only firing onchange
…but is backward compatible to IE8. This does deprecate the ability to attach to a modal by :title, but truthfully that's not useful. There should only be one modal dialog active at any one time. If that's necessary you can always use a Watir::Wait method to wait for the right ie.modal_dialog.title to appear.
…dow and load up the code in your local path. This makes it possible to interact in IRB without having to install gems.