Copilot Not Working

How to Locate the Microsoft Copilot Designer Button with Selenium WebDriver

Camila Milosovich Sep 28, 2026 869 views

Question details

The user needs to locate and click the Designer button on the Microsoft Copilot website using Selenium WebDriver but is unable to find the element.

Locating the Microsoft Copilot Designer Button with Selenium WebDriver

Product: Microsoft Copilot
Device & OS: not provided
Scenario: Automating browser interactions and UI testing on the Microsoft Copilot website.
Observed behavior: Selenium WebDriver throws an element not found exception because the Designer button may load dynamically, be nested in an iframe, or exist within a shadow DOM component.

Before you start

Ensure you have the latest version of Selenium WebDriver installed in your project and that your browser driver matches your current browser version to avoid compatibility errors.

Solution 1Recommended

Use Explicit Waits with a Stable Selector

Implement explicit waits and reliable CSS/XPath selectors to ensure the dynamically loaded button is clickable before interacting with it.

Web pages like Microsoft Copilot render elements dynamically. If Selenium attempts to interact with the Designer button before it is fully rendered, the action will fail. Avoid long, absolute XPaths as they break easily during UI updates.

Choose a stable locator strategy

In your Selenium script, define the locator using a partial attribute match, such as By.cssSelector("button[aria-label*='Designer']") or By.xpath("//button[contains(@aria-label, 'Designer')]").

Initialize an explicit wait

Create a WebDriverWait instance in your code, for example: WebDriverWait wait = new WebDriverWait(driver, Duration.ofSeconds(10));

Wait for the element to become clickable

Use ExpectedConditions to wait for the element: WebElement designerButton = wait.until(ExpectedConditions.elementToBeClickable(By.cssSelector("button[aria-label*='Designer']")));

Execute the click action

Once the button is returned by the wait condition, trigger the interaction by calling designerButton.click();

Use Explicit Waits with a Stable Selector

Best Practice: Using expected conditions for clickability is far more reliable than generic thread sleeps or implicit waits when handling modern dynamic web applications.

Solution 2

Switch to Iframe or Query Shadow DOM

Check if the button is trapped inside an isolated DOM environment like an iframe or shadow root, which prevents standard driver commands from finding it.

Free Microsoft Office alternative

Document Your Automation Scripts Better with WPS Office

While troubleshooting complex web automation tasks for platforms like Microsoft Copilot, you need a robust office suite to document your test cases and log automation reports. WPS Office is a free, lightweight, and fully compatible alternative to Microsoft Office.

1. Download the software: Visit the official WPS website and download the free installation package for your operating system.
2. Install and launch: Follow the on-screen instructions to install the suite and open WPS Office.
3. Open your test reports: Drag and drop your existing Microsoft Word or Excel test documentation directly into WPS Office without losing any formatting.

Fully compatible with Microsoft Word, Excel, and PowerPoint formats.Easily draft test plans and script documentation with integrated AI writing assistants.Lightweight design that won't slow down your machine while running heavy WebDriver instances.Familiar ribbon-style UI for a seamless migration from Microsoft Office.

microsoft office alternative - wps office

Frequently Asked Questions

Why does Selenium throw a NoSuchElementException for the Designer button?

This happens when Selenium tries to locate the element before the browser's JavaScript has finished rendering it. Implementing an explicit wait ensures the WebDriver pauses until the button actually exists in the DOM.

How do I know if an element is inside an iframe?

Open your browser's Developer Tools (F12), right-click the Copilot Designer button, and select 'Inspect'. Look at the hierarchy in the Elements tab; if an <iframe> tag wraps the button's parent nodes, it is inside an iframe.

Why shouldn't I use absolute XPaths in Selenium testing?

Absolute XPaths rely on the exact structural path from the root HTML element down to the target. Because modern websites like Copilot are constantly updated, any small layout change will break an absolute XPath, resulting in fragile and unmaintainable test scripts.

What is a Shadow DOM and how does it affect Selenium?

A Shadow DOM is a web standard used to encapsulate HTML and CSS within web components. Selenium's standard driver.findElement() cannot penetrate a shadow boundary. You must first locate the shadow host and use getShadowRoot() to access the internal elements.

Microsoft Copilot Issues