tianyao1111
tianyao1111
> https://stackoverflow.com/questions/55492695/javascript-error-arguments0-scrollintoview-is-not-a-function-using-selenium-o ? Could you share the full appium server log as well? I have also read this article and I used find_ Element. And everything was normal before I...
> > https://stackoverflow.com/questions/55492695/javascript-error-arguments0-scrollintoview-is-not-a-function-using-selenium-o ? Could you share the full appium server log as well? > > I have also read this article and I used find_ Element. And everything was...
> Possibly chromedriver knows the reason. loglevel debug may show more info. `appium:showChromedriverLog` capability is also. > > Basically the response came from chromedriver because your log had set context...
> Please add `appium:showChromedriverLog` to print chromedriver logs This is the log after opening appium: showChromedriverLog ``` [35m[Appium][39m Welcome to Appium v1.22.0 [35m[Appium][39m Non-default server args: [35m[Appium][39m sessionOverride: true [35m[Appium][39m...
> Hm, as the below error, the error itself came from chromedriver v81, not Appium own implementation. > > ``` > �[35m[HTTP]�[39m �[37m-->�[39m �[37mPOST�[39m �[37m/wd/hub/session/5e0d7962-7781-4d80-aed0-78fd1beb4e1a/execute/sync�[39m > �[35m[HTTP]�[39m �[90m{"script":"return arguments[0].scrollIntoView(true);","args":[{"element-6066-11e4-a52e-4f735466cecf":"0.47396339724855663-4"}]}�[39m >...
> > Hm, as the below error, the error itself came from chromedriver v81, not Appium own implementation. > > ``` > > �[35m[HTTP]�[39m �[37m-->�[39m �[37mPOST�[39m �[37m/wd/hub/session/5e0d7962-7781-4d80-aed0-78fd1beb4e1a/execute/sync�[39m > > �[35m[HTTP]�[39m...
> > The following is the log of selenium running with Chrome v81, and there were no errors reported in the scoreIntoView > > The attached log had a 500...