Hi Bret, Following are the features that are there in FireWatir but not in Watir. Some of these can be impelemented easily but some of them really need a thought:
1. Accessing element using any attribute that is there in the rendered HTML on the browser. 2. There is method_missing function in FireWatir which catches the methods that are called for an element but are not implemented. This method will then call those methods on the element and will return the results appropriately. This can be useful in case user accesses an element using XPATH whose class is not there like MAP (which is there in Watir, but not in Firewatir) and user tries to fire or execute the method that is defined for the element but not implemented. 3. Platform Indpendence: This functionality FireWatir inherits from its implementation i.e. usage of JSSh. 4. Running on Remote machine: This functionality FireWatir also inherits from its implementation i.e. usage of JSSh. That is what I can think of as of now. Regards, Regards Prema On 1/31/07, Bret Pettichord <[EMAIL PROTECTED] > wrote:
Prema Arya wrote: > Yes we can do it in FireWatir also: > > puts ff.text_field(:custom, "custom").value > <input id="id" value="Prema" custom="custom"> We do not support this in Watir::IE. Should we? Are there other features that were added to FireWatir that aren't in Watir::IE? As we think about recombining all the different versions of Watir, we will have to support a common API across the versions, so we will need to have a way of reaching agreement on these kinds of issues. Bret _______________________________________________ Wtr-general mailing list Wtr-general@rubyforge.org http://rubyforge.org/mailman/listinfo/wtr-general
-- Prema Arya
_______________________________________________ Wtr-general mailing list Wtr-general@rubyforge.org http://rubyforge.org/mailman/listinfo/wtr-general
