Added ElementNotVisibleException to Error Documentation (#1971)

Added ElementNotVisibleException

Author: shbenzer

website_and_docs/content/documentation/webdriver/troubleshooting/errors/_index.en.md

@@ -179,3 +179,19 @@ This exception occurs when Selenium tries to interact with an element that is no
 2. Ensure locators uniquely identify the intended element to avoid incorrect matches.  
 3. Check if the element is visible on the page before interacting with it. Use scrolling to bring the element into view, if required.  
 4. Use explicit waits to ensure the element is interactable before performing actions.
+
+## ElementNotVisibleException
+
+This exception is thrown when the element you are trying to interact with _is_ present in the DOM, but is not visible. 
+
+### Likely Cause
+
+This can occur in several situations:
+* Another element is blocking your intended element
+* The element is disabled/invisible to the user
+
+### Possible Solutions
+
+This issue cannot always be resolved on the user's end, however when it can it is usually solved by the following: 
+using an explicit wait, or interacting with the page in such a way to make the element visible 
+(scrolling, clicking a button, etc.)

website_and_docs/content/documentation/webdriver/troubleshooting/errors/_index.ja.md

@@ -175,3 +175,20 @@ This exception occurs when Selenium tries to interact with an element that is no
 2. Ensure locators uniquely identify the intended element to avoid incorrect matches.  
 3. Check if the element is visible on the page before interacting with it. Use scrolling to bring the element into view, if required.  
 4. Use explicit waits to ensure the element is interactable before performing actions.
+
+## ElementNotVisibleException
+
+This exception is thrown when the element you are trying to interact with _is_ present in the DOM, but is not visible. 
+
+### Likely Cause
+
+This can occur in several situations:
+* Another element is blocking your intended element
+* The element is disabled/invisible to the user
+
+### Possible Solutions
+
+This issue cannot always be resolved on the user's end, however when it can it is usually solved by the following: 
+using an explicit wait, or interacting with the page in such a way to make the element visible 
+(scrolling, clicking a button, etc.)
+

website_and_docs/content/documentation/webdriver/troubleshooting/errors/_index.pt-br.md

@@ -175,3 +175,19 @@ This exception occurs when Selenium tries to interact with an element that is no
 2. Ensure locators uniquely identify the intended element to avoid incorrect matches.  
 3. Check if the element is visible on the page before interacting with it. Use scrolling to bring the element into view, if required.  
 4. Use explicit waits to ensure the element is interactable before performing actions.
+
+## ElementNotVisibleException
+
+This exception is thrown when the element you are trying to interact with _is_ present in the DOM, but is not visible. 
+
+### Likely Cause
+
+This can occur in several situations:
+* Another element is blocking your intended element
+* The element is disabled/invisible to the user
+
+### Possible Solutions
+
+This issue cannot always be resolved on the user's end, however when it can it is usually solved by the following: 
+using an explicit wait, or interacting with the page in such a way to make the element visible 
+(scrolling, clicking a button, etc.)

website_and_docs/content/documentation/webdriver/troubleshooting/errors/_index.zh-cn.md

@@ -178,3 +178,19 @@ Actions class with `Actions.moveToElement(element)`.
 2. 确保定位器唯一标识目标元素，以避免错误匹配。  
 3. 在与元素交互之前，检查其是否在页面上可见。如果需要，将元素滚动到视图中。  
 4. 使用显式等待以确保元素在执行操作前可交互。
+
+## ElementNotVisibleException
+
+This exception is thrown when the element you are trying to interact with _is_ present in the DOM, but is not visible. 
+
+### Likely Cause
+
+This can occur in several situations:
+* Another element is blocking your intended element
+* The element is disabled/invisible to the user
+
+### Possible Solutions
+
+This issue cannot always be resolved on the user's end, however when it can it is usually solved by the following: 
+using an explicit wait, or interacting with the page in such a way to make the element visible 
+(scrolling, clicking a button, etc.)