fix: harden windows export readiness

A flaky windows-latest Chrome CI run timed out waiting for document.readyState during image_to_svg_string even though the page finished loading immediately afterward.

Increase the Windows-only document readiness timeout and fix the plotly container wait loop so the timeout path behaves as intended.

Signed-off-by: Mridankan Mandal <xerontitan90@gmail.com>

Author: RedZapdos123

plotly_static/src/lib.rs

@@ -1059,7 +1059,7 @@ impl AsyncStaticExporter {
         client.goto(&url).await?;
 
         #[cfg(target_os = "windows")]
-        Self::wait_for_document_ready(&client, std::time::Duration::from_secs(10)).await?;
+        Self::wait_for_document_ready(&client, std::time::Duration::from_secs(20)).await?;
 
         // Wait for Plotly container element
         #[cfg(target_os = "windows")]
@@ -1200,13 +1200,13 @@ impl AsyncStaticExporter {
             if has_el.as_bool().unwrap_or(false) {
                 return Ok(());
             }
+            if start.elapsed() > timeout {
+                return Err(anyhow!(
+                    "Timeout waiting for #plotly-html-element to appear in DOM"
+                ));
+            }
+            tokio::time::sleep(std::time::Duration::from_millis(50)).await;
         }
-        if start.elapsed() > timeout {
-            return Err(anyhow!(
-                "Timeout waiting for #plotly-html-element to appear in DOM"
-            ));
-        }
-        tokio::time::sleep(std::time::Duration::from_millis(50)).await;
     }
 
     #[cfg(target_os = "windows")]