[13selenium] 15p0deje 04force-pushed 06outdate-jna from 143b8a2b0 to 142b08036: 02https://git.io/v9nTG
13selenium/06outdate-jna 142b08036 15Alex Rodionov: Prevent JNA library conflicts on AppVeyor...
Mayestril has quit
jimpurbrick joined the channel
michl68 has quit
[13selenium] 15p0deje merged 06outdate-jna into 06master: 02https://git.io/v9nkg
[13selenium] 15p0deje 04force-pushed 06rb-handshake from 14f45ca34 to 1438efaf1: 02https://git.io/vSPOI
13selenium/06rb-handshake 1438efaf1 15Alex Rodionov: Support both OSS and W3C dialects in Ruby bindings...
[13selenium] 15p0deje 04deleted 06outdate-jna at 142b08036: 02https://git.io/v9nkw
[13selenium] 15barancev pushed 1 new commit to 06master: 02https://git.io/v9nIc
13selenium/06master 1491f9f2a 15Alexei Barantsev: Fixing key of pageLoad timeout
NOTICE: Project Build_All_Java build #7395: STILL FAILING in 14 min: http://ci.seleniumhq.org:8080/job/Build_All_Java/7395/
sanscoeur joined the channel
ussher_
AutomatedTester: the issue I ran into was I was doing a wait->until-> expectedCondition( elementToBeClickable ). that passed, then I 'that same element'->click() which would fail because of 308. so needed to add a wait/sleep/pause in there.
have since added a waitForPageToLoad() class that checks the document.ready state and that seams to get around it as instructed in the comments in issue 308
AutomatedTester
ussher_: thats now fixed in Firefox 55. the discussion was also around sendKeys from the way I read it
ussher_
so it was just a guess from me that if he added a wait/pause/sleep before the send keys maybe that would help.
NOTICE: Project Build_All_Java build #7396: STILL FAILING in 10 min: http://ci.seleniumhq.org:8080/job/Build_All_Java/7396/
PeterJones: it's because of the Firefox version you are using
can you update to 53?
if you can't, you'll need to downgrade selenium and geckodriver
PeterJones
<lucast> Thanks I will upgrade to FF53 now
<lucast> Thanks I will upgrade to FF52 is it?
lucast
i *think* 52 should work
PeterJones
<lucast> Thanks, you the MAN!
wewlad
WhereIsMySpoon: yeah, you are right. Looks like I've found a way to disable those notifications and I hope that helps, but turns out that selenium creates a new firefox profile each time, how to push some changes that'll be hooked by all new profiles?
WhereIsMySpoon
you need to make your own profile and load it, wewlad
there are classes for this
lucast
like online classes?
wewlad
uh, I don't want to mess with that :c
I'd better try to add user.js to firefox dir
AutomatedTester
wewlad: there is FirefoxProfile class in the python bindings to do the work for you
wewlad
AutomatedTester: nah, I've just added a pref to the defaults for all firefox profiles
this way it solves the problems with all firefox profiles on this vm, not just the ones ran by selenium