We put this in late yesterday and our numbers this morning were much better. When we encounter the problem, we're doing something similar to what Ramon is suggesting, but we are calling a close on the element rather than a terminate for the root Chrome. We are now spying the window in win32 mode. We found something that seems to resolve 95% of cases. So rather than use 'Equals' you choose 'Wildcard' and change the attribute value 'Customer System - *' Either exclude the offending attribute from the element definition, or change the Match Type to something other than 'Equals' in order to introduce the flexibility capable of working around the variation.Ī basic example of this is where the window title of an app is 'Customer System - Mrs J Smith' when you spy it, but you know that you'll be looking at other customer records at run time. If this does turn out to be the issue then you've two choices. And as Saaj says, things like Path and Class Name are usually the one to look at first. One or more of the attribute values may have changed, and one way to try and see this is by creating a temporary 'twin' element and then comparing it to the original. Hi Tracy - just to add to Saaj's advice, it sounds like the element 'definition' that was captured during dev does not fit the state of the application at runtime. Subject: Issues With Chrome Objects Finding Elements Those of you who have upgraded to 7.0 - what percentage of improvement have you seen? Those of you who have had this issue, have you tried switching to Edge? Does that buy us anything? An upgrade isn't something that can be done quickly.ĭoes anyone has any techniques to work around this issue while staying on 6.9? My co-workers have found forum discussions about this type of thing being more prevalent with 6.9 that advise that 7.0 is more stable. We re-spy it and it will work for that instance, but a few hours or days later it gets the same issue. We built Additor for Chrome to help you easily collect web content like news articles, PDF reports, Youtube videos, and etc. You can write notes, build a wiki, and collaborate on the same page. We can watch and see that element is there, but it can't be found. Featured on Product Hunt and Chrome Web Store Additor is your flexible knowledge base to organize various types of content, even with your team. But once in place, we find that sometimes the object doesn't find the element on the screen. We spy elements in browser mode, test the process and everything works fine. We are having issues with our conversion to Chrome for our web apps.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |