Re: [Wtr-general] bug with text_fields.show

in Jira, issue 140 http://jira.openqa.org/browse/WTR-140 - Original Message - From: "Bret Pettichord" <[EMAIL PROTECTED]> To: Sent: Tuesday, January 30, 2007 12:56 PM Subject: Re: [Wtr-general] bug with text_fields.show > Paul Rogers wrote: >> This seems to

Re: [Wtr-general] BUG: Using XPath

On 1/29/07, Prema Arya <[EMAIL PROTECTED]> wrote: Please find the attached patch fixing the xpath issue. Thanks. This has been committed to trunk. http://svn.openqa.org/fisheye/changelog/watir?cs=1150 Bret ___ Wtr-general mailing list Wtr-general@r

Re: [Wtr-general] bug with text_fields.show

Paul Rogers wrote: > This seems to be the same issue as wtr-93 ( > http://jira.openqa.org/browse/WTR-93 ) but for text fields and areas. Could you please report this issue in Jira? Bret ___ Wtr-general mailing list Wtr-general@rubyforge.org http://rubyf

[Wtr-general] bug with text_fields.show

irb(main):012:0> ie.showAllObjects ---Objects in page - text name=aa id= value= alt= textarea name=hidden id=hvalue= => nil irb(main):013:0> ie.text_fields.show index id

Re: [Wtr-general] BUG: Using XPath

Hi, Please find the attached patch fixing the xpath issue. Regards, Prema On 1/25/07, Bret Pettichord <[EMAIL PROTECTED]> wrote: On 1/25/07, Prema Arya <[EMAIL PROTECTED]> wrote: > > This change should be checked-in in the main branch also, Bret can you > give me access right to check-in? o

Re: [Wtr-general] BUG: Using XPath

Željko Filipin wrote: > Patching Code is Easy in Ruby by Bret Pettichord > http://www.io.com/~wazmo/blog/archives/2006_09.html#000241 > That article describes two ways of creating a patch. Since writing it, i have learned that the fir

Re: [Wtr-general] BUG: Using XPath

thanks for the link Zeljko, always wondered how patches worked. - Posted via Jive Forums http://forums.openqa.org/thread.jspa?threadID=6275&messageID=17660#17660 ___ Wtr-general mailing l

Re: [Wtr-general] BUG: Using XPath

On 1/25/07, Bret Pettichord <[EMAIL PROTECTED]> wrote: Please submit a patch. And here is explanation how to make a patch: Patching Code is Easy in Ruby by Bret Pettichord http://www.io.com/~wazmo/blog/archives/2006_09.html#000241 -- Zeljko Filipin zeljkofilipin.com _

Re: [Wtr-general] BUG: Using XPath

On 1/25/07, Prema Arya <[EMAIL PROTECTED]> wrote: This change should be checked-in in the main branch also, Bret can you give me access right to check-in? or someone else also can check-in the change. Please submit a patch. ___ Wtr-general mailing l

[Wtr-general] BUG: Using XPath

Hi, I was trying to get the from table as asked by Brad http://www.mail-archive.com/wtr-general@rubyforge.org/msg06677.html. I was using element_by_xpath and it didn't work and there was no reason why it should not work. After investigating I came across the function "create_rexml_document_obj

Re: [Wtr-general] Bug in fileField SetComboBoxText

Paul Rogers explained it before: "its a security thing in IE. It wont let you set a file fields value from script. Because you could have a file input in a hidden div, and have script enter the filename of some important file and then upload it without the user being aware of it." Zeljko -- http

[Wtr-general] Bug in fileField SetComboBoxText

I ran into an issue with the fileField.set method not setting the text I passed into it. I found that the issue was the call inside of winClicker.rbto the set_text method from the setComboBoxText method. The solution is to make your setComboBoxText method inside winClicker.rblook like the follow

Re: [Wtr-general] BUG: New IE windows share session state with existingopen windows

Please do not take this comment the wrong way, but this is the second time someone has mentioned -- to me -- that this might be an "inappropriate" topic for this forum. Please read the subject line again. Someone asked about "session states" being "shared" . . . in the context of Watir. I rep

Re: [Wtr-general] BUG: New IE windows share session state with existingopen windows

it is intended behavior, using globals can cause problems if you are not careful and AWARE of how they work in Ruby and Rails. Their behavior is very poorly documented, where it is documented at all. Lonny Eachus == Subject: Re: [Wtr-general] BUG

Re: [Wtr-general] BUG: New IE windows share session state with existingopen windows

>I see three ways this could happen, there may be more: (1) The variable "global_foo" is truly "global" on that server from the moment it is instantiated, and remains in memory even when there is no "running code". This is contrary to the way I understood globals to function . . . in which c

Re: [Wtr-general] BUG: New IE windows share session state with existingopen windows

On 6/7/06, Lonny Eachus <[EMAIL PROTECTED]> wrote: We had a server set up using multiple Mongrels with a lighttpd front end. A server will wait for an http request to come in, and fire off our Rails application. The program exits when done (i.e., the controller .rb runs to completion, no

Re: [Wtr-general] BUG: New IE windows share session state with existingopen windows

d, and then completed. The program exits. The next http request to come in is a different "session".  We are not storing cookies or any other "session" data in any way. Yet there is no doubt that global variables were being preserved between two different "sessions"

Re: [Wtr-general] BUG: New IE windows share session state with existingopen windows

On 6/6/06, Lonny Eachus <[EMAIL PROTECTED]> wrote: Our group has also found that global variables can carry over between separate runs of the same application, probably due to server caching. If a global variable was set during one run of the application, and not explicitly set to somet

Re: [Wtr-general] BUG: New IE windows share session state with existingopen windows

runs, just as they should. Lonny Eachus == Subject: Re: [Wtr-general] BUG: New IE windows share session state with existingopen windows From: "Michael Bolton" <[EMAIL PROTECTED]>

Re: [Wtr-general] BUG: New IE windows share session state with existingopen windows

riginal Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Schmidt Sent: June 6, 2006 12:50 PM To: wtr-general@rubyforge.org Subject: Re: [Wtr-general] BUG: New IE windows share session state with existingopen windows There's another issue which may be affecting your

Re: [Wtr-general] BUG: New IE windows share session state with existingopen windows

There's another issue which may be affecting your test that is also NOT a Watir bug. Sessions are often set by having a server save a session ID cookie on the IE's PC. For IE, these cookies are saved in a per-user directory. If you run multiple IE's to the same site then the cookies can be o

Re: [Wtr-general] BUG: New IE windows share session state with existingopen windows

PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Xi Chen Sent: June 6, 2006 5:21 AM To: wtr-general@rubyforge.org Subject: [Wtr-general] BUG: New IE windows share session state with existingopen windows Hi Scott I tried to run the following ie_array = Array.new(3) ie0 = WIN32OLE.new('Shell

[Wtr-general] BUG: New IE windows share session state with existing open windows

Hi Scott I tried to run the following ie_array = Array.new(3) ie0 = WIN32OLE.new('Shell.Application') system "c:\\Program Files\\Internet Explorer\\iexplore.exe" ie0 = IE.attach(:title,'Google') #my IE default page is Google ie0.goto("http://localhost:8080/kmdm8/signon.jsp";) ie_arra

[Wtr-general] bug?

Is this a bug or what? written below is a part of my code. it just runs a number of threads. However when i make it to loop 3 or more times. it returns an error in freeride, but not in scite editor. attached below is the console output for the error. Please advise. thanks. #no error 2.

Re: [Wtr-general] bug in text_field.to_s

Thanks for the report. It's been logged. http://rubyforge.org/tracker/index.php?group_id=104&atid=487 At 09:31 AM 7/26/2005, you wrote: There seems to be a bug in text_field.to_s: - HTML (valid): http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";> - IRB: irb require 'watir' ie = Wa

[Wtr-general] bug in text_field.to_s

There seems to be a bug in text_field.to_s: - HTML (valid): http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";> http://www.w3.org/1999/xhtml"; lang="en" xml:lang="en"> textarea - IRB: irb require 'watir' ie = Watir::IE.attach(:title, //) ie.textField(:index, 1).to_s - OU

RE: [Wtr-general] bug resolution

At 01:15 AM 7/26/2005, [EMAIL PROTECTED] wrote: I don't know the code to spawn a new process in watir. http://wtr.rubyforge.org/wiki/wiki.pl?FrequentQuestions _ Bret Pettichord www.pettichord.com ___ Wtr-general mailing list W

RE: [Wtr-general] bug resolution

I don't know the code to spawn a new process in watir. sorry for the idiot question. -jan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Bret Pettichord Sent: Tuesday, July 26, 2005 1:59 PM To: wtr-general@rubyforge.org Subject: Re: [Wtr-general

Re: [Wtr-general] bug resolution

At 07:24 PM 7/25/2005, [EMAIL PROTECTED] wrote: http://rubyforge.org/pipermail/wtr-general/2005-June/002240.html will this bug be fixed with the new release of watir? (pls see link above) No. Currently the best approach is to spawn a new process. and what's correct way of invoking WIN32OLE.ne

[Wtr-general] bug resolution

http://rubyforge.org/pipermail/wtr-general/2005-June/002240.html will this bug be fixed with the new release of watir? (pls see link above) and what's correct way of invoking WIN32OLE.new('Shell.Application') with internet explorer in Watir? Thanks! Jan M. Montano QA Lead / Developer Regi

Re: [Wtr-general] bug in text field

  Hi, I volunteer for adding a unit test for this feature. Just drop me a mail stating what all should be in the unit test. Regards, Angrez On Fri, 15 Jul 2005 Bret Pettichord wrote : >I have an app with a date text field. After entering the text, the app does some date checking. For example,

[Wtr-general] bug in text field

I have an app with a date text field. After entering the text, the app does some date checking. For example, if you enter 1/1/75, it turns it into 01/01/1975. When i entered text using watir (text_field().set('/1/1/75)'), the date checking doesn't happen. The fix is to trigger an onblur event