On Jul 25, 9:02 pm, Chuck van der Linden <[email protected]> wrote: > I presume the dropping of FireWatir is due to issues with a lack of > JSSH extensions for current versions? We might want to say something > specific in that regard in the release notes, and direct Firefox users > to Watir-Webdriver. (otherwise people new to the party may be > confused and think we've all been co-opted by MS, force-fed 'IE- > Koolaid' or something similar. After all, if you don't know the 'why' > dropping firewatir seems on the surface of it, kinda insane.
Yes, it's due to JSSH extension. Good idea, we should point it out in the changelog. Will do before release. > > One request for anyone working on updating the docs such as the > supported elements table (http://wiki.openqa.org/display/WTR/HTML > +Elements+Supported+by+Watir), it might make sense at this point to > 'archive' the existing watir 1.x page as is with a v1 tacked onto the > end of the URL. Place headers on both pages indicating the 'as of' > version for the docs, and a link to the old/new version > respectively. That would make it easier for anyone hanging back to > find appropriate docs. > > If someone who knows the wiki stuff better than I can create the > 'archive' page, I might be able to find time this week to take a hack > at updating that doc (which is one I always find highly useful) for > the v2 version. (since I have a bit more free time at the moment due > to being between employers) And yes, docs should be updated. You can mark all elements (except new browser window) with a checkbox for "multiple attributes", :xpath and :css for sure. Jarmo -- 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]
