update wait documentation

website_and_docs/content/documentation/webdriver/support_features/colors.en.md

@@ -1,7 +1,7 @@
 ---
 title: "Working With Colors"
 linkTitle: "Colors"
-weight: 1
+weight: 3
 aliases: [
 "/documentation/en/support_packages/working_with_colours/",
 "/documentation/support_packages/working_with_colours/",

website_and_docs/content/documentation/webdriver/support_features/colors.ja.md

@@ -1,7 +1,7 @@
 ---
 title: "色を扱う"
 linkTitle: "色を扱う"
-weight: 1
+weight: 3
 aliases: [
 "/documentation/ja/support_packages/working_with_colours/",
 "/ja/documentation/support_packages/working_with_colours/",

website_and_docs/content/documentation/webdriver/support_features/colors.pt-br.md

@@ -1,7 +1,7 @@
 ---
 title: "Trabalhando com cores"
 linkTitle: "Trabalhando com cores"
-weight: 1
+weight: 3
 aliases: [
 "/documentation/pt-br/support_packages/working_with_colours/",
 "/pt-br/documentation/support_packages/working_with_colours/",

website_and_docs/content/documentation/webdriver/support_features/colors.zh-cn.md

@@ -1,7 +1,7 @@
 ---
 title: "同颜色一起工作"
 linkTitle: "颜色"
-weight: 1
+weight: 3
 aliases: [
 "/documentation/zh-cn/support_packages/working_with_colours/",
 "/zh-cn/documentation/support_packages/working_with_colours/",

website_and_docs/content/documentation/webdriver/support_features/expected_conditions.en.md

@@ -0,0 +1,43 @@
+---
+title: "Waiting with Expected Conditions"
+linkTitle: "Expected Conditions"
+weight: 1
+description: >
+  These are classes used to describe what needs to be waited for.
+---
+
+Expected Conditions are used with [Explicit Waits](({{< ref "waits#explicit-waits" >}})).
+Instead of defining the block of code to be executed with a _lambda_, an expected
+conditions method can be created to represent common things that get waited on. Some
+methods take locators as arguments, others take elements as arguments.
+
+These methods can include conditions such as:
+
+* element exists
+* element is stale
+* element is visible
+* text is visible
+* title contains specified value
+
+{{< tabpane text=true langEqualsHeader=true >}}
+{{% tab header="Java" %}}
+[Expected Conditions Documentation](https://www.selenium.dev/selenium/docs/api/java/org/openqa/selenium/support/ui/ExpectedConditions.html)
+{{< badge-code >}}
+{{% /tab %}}
+{{< tab header="Python" >}}
+[Expected Conditions Documentation](https://www.selenium.dev/selenium/docs/api/py/webdriver_support/selenium.webdriver.support.expected_conditions.html)
+{{< badge-code >}}
+{{< /tab >}}
+{{< tab header="CSharp" >}}
+.NET stopped supporting Expected Conditions in Selenium 4 to minimize maintenance hassle and redundancy.
+{{< /tab >}}
+{{< tab header="Ruby" >}}
+Ruby makes frequent use of blocks, procs and lambdas and does not need Expected Conditions classes
+{{< /tab >}}
+{{< tab header="JavaScript" >}}
+{{< badge-code >}}
+{{< /tab >}}
+{{< tab header="Kotlin" >}}
+{{< badge-code >}}
+{{< /tab >}}
+{{< /tabpane >}}

website_and_docs/content/documentation/webdriver/support_features/expected_conditions.ja.md

@@ -0,0 +1,43 @@
+---
+title: "Waiting with Expected Conditions"
+linkTitle: "Expected Conditions"
+weight: 1
+description: >
+  These are classes used to describe what needs to be waited for.
+---
+
+Expected Conditions are used with [Explicit Waits](({{< ref "waits#explicit-waits" >}})).
+Instead of defining the block of code to be executed with a _lambda_, an expected
+conditions method can be created to represent common things that get waited on. Some
+methods take locators as arguments, others take elements as arguments.
+
+These methods can include conditions such as:
+
+* element exists
+* element is stale
+* element is visible
+* text is visible
+* title contains specified value
+
+{{< tabpane text=true langEqualsHeader=true >}}
+{{% tab header="Java" %}}
+[Expected Conditions Documentation](https://www.selenium.dev/selenium/docs/api/java/org/openqa/selenium/support/ui/ExpectedConditions.html)
+{{< badge-code >}}
+{{% /tab %}}
+{{< tab header="Python" >}}
+[Expected Conditions Documentation](https://www.selenium.dev/selenium/docs/api/py/webdriver_support/selenium.webdriver.support.expected_conditions.html)
+{{< badge-code >}}
+{{< /tab >}}
+{{< tab header="CSharp" >}}
+.NET stopped supporting Expected Conditions in Selenium 4 to minimize maintenance hassle and redundancy.
+{{< /tab >}}
+{{< tab header="Ruby" >}}
+Ruby makes frequent use of blocks, procs and lambdas and does not need Expected Conditions classes
+{{< /tab >}}
+{{< tab header="JavaScript" >}}
+{{< badge-code >}}
+{{< /tab >}}
+{{< tab header="Kotlin" >}}
+{{< badge-code >}}
+{{< /tab >}}
+{{< /tabpane >}}

website_and_docs/content/documentation/webdriver/support_features/expected_conditions.pt-br.md

@@ -0,0 +1,43 @@
+[expected_conditions.ja.md](expected_conditions.ja.md)---
+title: "Waiting with Expected Conditions"
+linkTitle: "Expected Conditions"
+weight: 1
+description: >
+  These are classes used to describe what needs to be waited for.
+---
+
+Expected Conditions are used with [Explicit Waits](({{< ref "waits#explicit-waits" >}})).
+Instead of defining the block of code to be executed with a _lambda_, an expected
+conditions method can be created to represent common things that get waited on. Some
+methods take locators as arguments, others take elements as arguments.
+
+These methods can include conditions such as:
+
+* element exists
+* element is stale
+* element is visible
+* text is visible
+* title contains specified value
+
+{{< tabpane text=true langEqualsHeader=true >}}
+{{% tab header="Java" %}}
+[Expected Conditions Documentation](https://www.selenium.dev/selenium/docs/api/java/org/openqa/selenium/support/ui/ExpectedConditions.html)
+{{< badge-code >}}
+{{% /tab %}}
+{{< tab header="Python" >}}
+[Expected Conditions Documentation](https://www.selenium.dev/selenium/docs/api/py/webdriver_support/selenium.webdriver.support.expected_conditions.html)
+{{< badge-code >}}
+{{< /tab >}}
+{{< tab header="CSharp" >}}
+.NET stopped supporting Expected Conditions in Selenium 4 to minimize maintenance hassle and redundancy.
+{{< /tab >}}
+{{< tab header="Ruby" >}}
+Ruby makes frequent use of blocks, procs and lambdas and does not need Expected Conditions classes
+{{< /tab >}}
+{{< tab header="JavaScript" >}}
+{{< badge-code >}}
+{{< /tab >}}
+{{< tab header="Kotlin" >}}
+{{< badge-code >}}
+{{< /tab >}}
+{{< /tabpane >}}

website_and_docs/content/documentation/webdriver/support_features/expected_conditions.zh-cn.md

@@ -0,0 +1,43 @@
+---
+title: "Waiting with Expected Conditions"
+linkTitle: "Expected Conditions"
+weight: 1
+description: >
+  These are classes used to describe what needs to be waited for.
+---
+
+Expected Conditions are used with [Explicit Waits](({{< ref "waits#explicit-waits" >}})).
+Instead of defining the block of code to be executed with a _lambda_, an expected
+conditions method can be created to represent common things that get waited on. Some
+methods take locators as arguments, others take elements as arguments.
+
+These methods can include conditions such as:
+
+* element exists
+* element is stale
+* element is visible
+* text is visible
+* title contains specified value
+
+{{< tabpane text=true langEqualsHeader=true >}}
+{{% tab header="Java" %}}
+[Expected Conditions Documentation](https://www.selenium.dev/selenium/docs/api/java/org/openqa/selenium/support/ui/ExpectedConditions.html)
+{{< badge-code >}}
+{{% /tab %}}
+{{< tab header="Python" >}}
+[Expected Conditions Documentation](https://www.selenium.dev/selenium/docs/api/py/webdriver_support/selenium.webdriver.support.expected_conditions.html)
+{{< badge-code >}}
+{{< /tab >}}
+{{< tab header="CSharp" >}}
+.NET stopped supporting Expected Conditions in Selenium 4 to minimize maintenance hassle and redundancy.
+{{< /tab >}}
+{{< tab header="Ruby" >}}
+Ruby makes frequent use of blocks, procs and lambdas and does not need Expected Conditions classes
+{{< /tab >}}
+{{< tab header="JavaScript" >}}
+{{< badge-code >}}
+{{< /tab >}}
+{{< tab header="Kotlin" >}}
+{{< badge-code >}}
+{{< /tab >}}
+{{< /tabpane >}}