Wait Until Element Is Visible and Wait Until Element Is Not Visible log about 45 kilobytes of JS code on DEBUG level

首先使用 SeleniumLibrary、Chrome 或 Firefox 以及 DEBUG 日志记录来复现该示例。跟踪 Wait Until Element Is Visible 和 Wait Until Element Is Not Visible 的实现，重点关注为什么 isDisplayed.js 会输出到日志中。当重复的可见性检查不再记录约 45 KB 的 JavaScript 负载，同时检查仍能正常工作时，即表示完成。

For issues

Steps to reproduce the issue

Can be reproduced with at least Chrome and Firefox.

*** Settings ***
Library    SeleniumLibrary

*** Test Cases ***
Test Case
   Open Browser    https://robotframework.org/    firefox
   Wait Until Element Is Visible    introduction
   Close Browser

Error messages and additional information

JavaScript code seems to originate from C:\Python37\Lib\site-packages\selenium\webdriver\remote\isDisplayed.js

Expected behavior and actual behavior

Expected behavior: visibility would be checked without logging JavaScript code.

Actual behavior: 45 056 bytes of JavaScript is logged each time Wait Until Element Is Visible or Wait Until Element Is Not Visible is called. Our recent log file exceeded 500 megabytes in size because these keywords were called over 10,000 times during the test run.

This is relatively new change as I don't remember seeing this in spring 2019.

Environment

Browser: Chrome 78, Firefox 70
Browser driver: ChromeDriver 78, GeckoDriver 0.26.0
Operating System: Windows 10
Libraries

• Robot Framework: 3.1.2
• Selenium: 3.141.0
• SeleniumLibrary: 4.1.0
• Interpreter: Python 3.7.4