Closed MattiSG closed 9 years ago
please provide a reproducible test case for us using "Selenium's native API" we don't have the time to look through the other project for a potential bug in it. Can reopen this bug if a concise reproducible test case is provided.
Does a series of JSONwire commands qualify, or do I really need to write Java to contribute bug reports?
that could be a start... you don't need java... we also have C#, python, ruby, javascript :)
thanks for the reproducible test case!
since it was fixed in the atoms, this should be fixed in chromedriver the next time they pull in the atoms and do a release.
will be available in firefox in the next release, or you could always build from source.
Great!
Looking at the referenced commit, I'm wondering if you won't get the exact same issue with all the different input type
s that are expected to give a value of type other than String
in JS. WDYT?
Matti Schneider ———— Written on a phone, please excuse the terseness. Rédigé sur un téléphone, veuillez excuser la brièveté.
I tried with a variety of other input types (from the html 5 spec) and only number exhibited this behavior. If others in the future do too, then we'll have to correct it then.
:+1:
Here is a test case that uses Watai:
(assuming you have a running Selenium Server)
Sorry, I have long forgotten Selenium’s native API.
Reproduced with v2.45 and v2.48.0, on both Firefox and Chrome.