RE: [Wtr-general] Next release ( 1.4)
This looks to be the same bug that was reported a week or 2 back. Its
been fixed and is checked
Thanks!
Paul
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Zeljko Filipin
Sent: 07 July 2005 04:25
To: wtr-general@rubyforge.org
Subject: RE: [Wtr-general] Next release ( 1.4)
Similar bug:
HTML:
html
body
a href= id=link_id name=link_namelink 1/a
input type=radio id=radio_id name=radio_name /
/body
/html
IRB:
irb
require 'watir'
ie = Watir::IE.attach(:title, //)
ie.radios.each { | item | puts item.id }
OUTPUT:
link_id
and it works ok if html is:
html
body
input type=radio id=radio_id name=radio_name /
a href= id=link_id name=link_namelink 1/a
/body
/html
-Original Message-
I looked at tracker at http://rubyforge.org/projects/wtr/ and I did not
find this bug (example is for 'id', but I reproduced it also for
'name'):
HTML:
html
body
a href= id=link_id name=link_namelink 1/a
input type=checkbox id=checkbox_id
name=checkbox_name /
/body
/html
IRB:
irb
require 'watir'
ie = Watir::IE.attach(:title, //)
ie.checkboxes.each { | item | puts item.id }
OUTPUT:
link_id
___
Wtr-general mailing list
Wtr-general@rubyforge.org
http://rubyforge.org/mailman/listinfo/wtr-general
___
Wtr-general mailing list
Wtr-general@rubyforge.org
http://rubyforge.org/mailman/listinfo/wtr-general
RE: [Wtr-general] Next release ( 1.4)
I am not shure if I undrestood, but I use something like this, if this is
what you meant:
class Web
def enter_text( text_field )
puts - entering text: #{ text_field.display } = #{
text_field.value }
@ie.textField( text_field.how, text_field.what ).set(
text_field.value )
end
end
-Original Message-
Class ObjectActions
def my_own_special_mrthod
# some code
end
end
Im sure not many, if anyone is doing this, but please let me know if you
are.
___
Wtr-general mailing list
Wtr-general@rubyforge.org
http://rubyforge.org/mailman/listinfo/wtr-general
Re: [Wtr-general] Next release ( 1.4)
At 10:09 PM 7/5/2005, Paul Rogers wrote:
can now specify a default attribute, eg
ie.default_attribute = :id
ie.text_field( 'abc1').set('Testing')
there is also a default for particular element types,
ie.set_default_attribute_for_element( :button , :id)
ie.button( 'b1').click
I think there are problems with both the interface and the implementation
of this. I've worked some on fixing these, but have more work to do.
I suggest removing this from the release so that we don't commit ourselves
to an interface we don't plan to support.
Bret
_
Bret Pettichord
www.pettichord.com
___
Wtr-general mailing list
Wtr-general@rubyforge.org
http://rubyforge.org/mailman/listinfo/wtr-general
Re: [Wtr-general] Next release ( 1.4)
At 10:09 PM 7/5/2005, Paul Rogers wrote: Now, one of the refactorings that has taken pace has the potential to break some code. I doubt it will happen to many people. If you are using code like the following in your scripts, please can you let me know, so we can try to accommodate you. Class ObjectActions def my_own_special_mrthod # some code end end Im sure not many, if anyone is doing this, but please let me know if you are. I renamed an internal class. Anyone using watir needs to understand that some interfaces are supported and others are internal to the tool, aren't intended for public consumption, and are subject to change. The class was renamed to Elements -- if you happen to have been referencing this class all you have to do is use the new name. Bret _ Bret Pettichord www.pettichord.com ___ Wtr-general mailing list Wtr-general@rubyforge.org http://rubyforge.org/mailman/listinfo/wtr-general
Re: [Wtr-general] Next release ( 1.4)
At 11:18 AM 7/6/2005, Chris Morris wrote: Is there anyway to help make this clearer to using watir? I believe Eclipse actually goes to packaging pains to put certain classes that are internal in packages called, internal, so it's hard for a user not to know they're working against interfaces that could change out from under them. This is a good idea. But i don't know if we're going to have this in place for 1.4. My understanding is that the only published/supported class is Watir::IE. Are there any others? _ Bret Pettichord www.pettichord.com ___ Wtr-general mailing list Wtr-general@rubyforge.org http://rubyforge.org/mailman/listinfo/wtr-general
Re: [Wtr-general] Next release ( 1.4)
Hi,
It will be very beneficial if Watir can support the
Javascript menus similar to the one in
http://www.cbc.ca, where links are declared in a
Javascript file that is not loaded in the DOM
Regards
Guru
--- Paul Rogers [EMAIL PROTECTED] wrote:
Some one today asked about the next release, which
was timely as Ive
been writing this email for a few days.
Im working on getting the next release out soon -
maybe next week.
The following bugs have been fixed:
table using id and reg exp is not found
checkboxes have extra events
wrong objects are sometimes found
wait for page load on new windows
flash for objects in table cells
checkbox#value exception (may have been done in
refactoring - need to
verify)
And the following new features
flash for forms
iterator objects now have a show method, eg
ie.buttons.show
can now specify a default attribute, eg
ie.default_attribute = :id
ie.text_field( 'abc1').set('Testing')
there is also a default for particular element
types,
ie.set_default_attribute_for_element(
:button , :id)
ie.button( 'b1').click
tablecell#colspan - returns the number of
columns the cell spans. Is
this method named correctly?
And some other possible bug fixes/new features if
time permits.
Fix for using :value
improve javascript popups handling ( ihave a few
ideas, details in a
separate email if I get to it)
find frame using :name and reg exp
frames iterator
show_windows
.style to be deprecated replaced with something
like .dhtml_class (
suggestions for method name please)
Now, one of the refactorings that has taken pace has
the potential to
break some code. I doubt it will happen to many
people. If you are using
code like the following in your scripts, please can
you let me know, so
we can try to accommodate you.
Class ObjectActions
def my_own_special_mrthod
# some code
end
end
Im sure not many, if anyone is doing this, but
please let me know if you
are.
Are there any other things that people need
urgently, or any bugs Im
missing?
Thanks
Paul
___
Wtr-general mailing list
Wtr-general@rubyforge.org
http://rubyforge.org/mailman/listinfo/wtr-general
___
Wtr-general mailing list
Wtr-general@rubyforge.org
http://rubyforge.org/mailman/listinfo/wtr-general
