Re: [wtr-general] HTML element order different in IE8 from IE7

2010-09-06 Thread Željko Filipin
On Sat, Sep 4, 2010 at 4:36 PM, Lisa Crispin lisa.cris...@gmail.com wrote: I tried to create a Jira account to enter this bug and got a npe, rats. Lisa, thanks for letting us know. I will contact Patrick Lightbody ( http://twitter.com/plightbo), he is in charge of Jira. Željko -- watir.com -

Re: [wtr-general] HTML element order different in IE8 from IE7

2010-09-04 Thread Lisa Crispin
Thanks, Ethan and Charley. I didn't write this script, and the person who did left a few years ago, so I can't say why he did what he did, but he wrote LOTS of scripts that parse html in this way. He was trying to make the scripts really flexible, and kind of act like a manual tester just trying

Re: [wtr-general] HTML element order different in IE8 from IE7

2010-09-04 Thread Lisa Crispin
I tried to create a Jira account to enter this bug and got a npe, rats. com.atlassian.jira.exception.DataAccessException: Group must not be null if trying to add or delete a user from it. at com.atlassian.jira.user.util.UserUtilImpl.validateParameters(UserUtilImpl.java:584) at

[wtr-general] HTML element order different in IE8 from IE7

2010-09-03 Thread Lisa Crispin
I had a script fail when running it on IE8, it's several years old and works fine on IE7. It's setting a radio button: ie.radio(:name, 'anniversaryDate', anniversary_date).set The value of anniversary_date is a date like '10-01-2008' (at least, in IE7), it's set by using regex to parse the html

Re: [wtr-general] HTML element order different in IE8 from IE7

2010-09-03 Thread Charley Baker
You've kind of nailed it with the irb session. That's a really brittle regex and best avoided, now I understand the IE7/8 thing, how and where the DOM attributes show up really doesn't matter for browsers, coding it this way would be a code smell. This should work: ie.radio(:name =

Re: [wtr-general] HTML element order different in IE8 from IE7

2010-09-03 Thread Ethan
There are several problems here. - The attributes of an html object aren't meant to be in any particular order; them changing is not really a bug. - Using a regexp to parse html is a fundamentally broken idea. - Why are you passing a third argument to #radio at all if you are just getting that