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 <[email protected]> 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) 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... > > > Jarmo > > > On Mar 22, 12:23 am, hillary <[email protected]> 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::MissingWayOfFindingObjectException: 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. [email protected] http://groups.google.com/group/watir-general [email protected]
