My agent could see the dropdown. It just couldn't pick anything.
The article discusses a technical issue encountered with a dropdown element in a Salesforce/Lightning support form embedded in a customer portal. The problem arose from the interaction between different layers of the Document Object Model (DOM) and how the agent's tool was unable to recognize the dropdown element. A patch was implemented to improve the element resolution process, allowing the tool to function correctly across iframes and shadow roots.
- ▪The dropdown element was not recognized due to the complexity of the DOM structure involving iframes and shadow roots.
- ▪The agent's tool used a simple query that did not account for nested elements, leading to the issue.
- ▪A patch was released to enhance the tool's ability to find elements by using a more comprehensive resolution method.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 3810102) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } אחיה כהן Posted on May 24 My agent could see the dropdown. It just couldn't pick anything. #ai #opensource #javascript #postmortem The agent had a list. I asked it to pick an item. It refused. Element not found Refresh. Same. So I opened DevTools and pasted in: document.querySelector('select[name="status"]') // null Enter fullscreen mode Exit fullscreen mode null. On a page that obviously had a dropdown. I could see it. I could click it. I could expand it with the mouse.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
