did pik add gemsets? It's not so much different versions of ruby that's a 
problem, but need to use different versions of watir if the direction of 
future versions of watir is html5. The comment below me suggested xpath 
which i hadn't thought of, so i'm going to try that. 

On Tuesday, March 27, 2012 3:35:57 PM UTC-7, Oscar.Rieken wrote:
>
> Pik is a tool to manage multiple versions of ruby on Windows. It can be 
> used from the Windows command line (cmd.exe), Windows PowerShell, or Git 
> Bash.
> https://github.com/vertiginous/pik 
>
> just so you know there is one out there :)
> if you post the html for the nav maybe there is another way
>
>
> On Tue, Mar 27, 2012 at 6:30 PM, hillary <weimar1...@gmail.com> wrote:
>
>> yeah it kinda broke all links to nav through a tab in the webapp. So i 
>> have to figure out a work around, because i can't really have the devs 
>> change it. The application i'm testing wasn't coded to any type of 
>> standards so it used name instead of id to tag links. 
>>
>> I'm going to be using watir to test both a legacy code base and a new mvc 
>> application (which uses html5) so i can't really go back to 2.0. I'm also 
>> on windows so I don't really have something like rvm to switch between 
>> gemsets to test both applications. 
>>
>> So far this has been the only stumbling block in the upgrade process. 
>>
>>
>>
>> On Tuesday, March 27, 2012 8:26:24 AM UTC-7, Jarmo Pertman wrote:
>>>
>>> Yes, we're trying to follow html5 standard now as watir-webdriver 
>>> does. I myself haven't used name for link even when using html4. 
>>> Hopefully there's not many things which will break. 
>>>
>>> Also, don't forget that Watir 3 will not be itself fully backwards 
>>> compatible. 
>>>
>>> Jarmo 
>>>
>>> On Mar 26, 10:19 pm, Chuck van der Linden <sqa...@gmail.com> wrote: 
>>> > Are we being strict about HTML5 for this stuff, because as near as I 
>>> can 
>>> > tell, it was a valid optional attribute for an anchor tag as of HTML4 
>>> > (http://www.w3schools.com/**tags/tag_a.asp<http://www.w3schools.com/tags/tag_a.asp>)
>>> >  
>>>  which means it would be 
>>> > perfectly valid HTML for many a website that was not yet upgraded to 
>>> HTML5 
>>> > to be using a name attribute with an anchor tag. 
>>> > 
>>> > 
>>> > 
>>> > 
>>> > 
>>> > 
>>> > 
>>> > On Friday, March 23, 2012 12:05:00 AM UTC-7, Jarmo Pertman wrote: 
>>> > 
>>> > > Short answer is yes. 
>>> > 
>>> > > All attributes got removed from all elements which are not valid for 
>>> > > that specific eleent. "name" is one of these examples, which is not 
>>> a 
>>> > > valid attribute for link. 
>>> > 
>>> > > Starting from Watir 3, "name" is only valid attribute for these 
>>> > > elements: 
>>> > > button; fieldset; input; keygen; output; select; textarea; form; 
>>> > > iframe; object; map; meta; param. 
>>> > 
>>> > > Check out the more specific list for other elements at 
>>> > 
>>> > >http://www.whatwg.org/specs/**web-apps/current-work/**
>>> multipage/section-i.<http://www.whatwg.org/specs/web-apps/current-work/multipage/section-i.>..
>>>  
>>>
>>> > 
>>> > > Jarmo 
>>> > 
>>> > > On Mar 22, 12:23 am, hillary <weimar1...@gmail.com> wrote: 
>>> > > > I had been identifying some links by name. I upgraded to rc3 and 
>>> now i 
>>> > > get 
>>> > > > an error. 
>>> > 
>>> > > > browser.link(:name, "#page_25").click 
>>> > 
>>> > > > Watir::Exception::**MissingWayOfFindingObjectExcep**tion: name is 
>>> an unknown 
>>> > > > way of finding a <a> element (#page_25)
>>
>>  -- 
>> Before posting, please read http://watir.com/support. In short: search 
>> before you ask, be nice.
>>  
>> watir-general@googlegroups.com
>> http://groups.google.com/group/watir-general
>> watir-general+unsubscr...@googlegroups.com
>>
>
>

-- 
Before posting, please read http://watir.com/support. In short: search before 
you ask, be nice.

watir-general@googlegroups.com
http://groups.google.com/group/watir-general
watir-general+unsubscr...@googlegroups.com

Reply via email to