<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <id>https://selenium.dev/selenium-ide/blog</id>
    <title>Selenium IDE Blog</title>
    <updated>2018-12-05T06:00:00Z</updated>
    <generator>Feed for Node.js</generator>
    <link rel="alternate" href="https://selenium.dev/selenium-ide/blog"/>
    <subtitle>The best place to stay up-to-date with the latest Selenium IDE news and events.</subtitle>
    <logo>https://selenium.dev/selenium-ide/img/selenium-ide128.png</logo>
    <rights>Copyright © 2019 Software Freedom Conservancy (SFC)</rights>
    <entry>
        <title type="html"><![CDATA[The Difficulties of Selecting Windows]]></title>
        <id>https://selenium.dev/selenium-ide/blog/2018/12/05/the-difficulties-of-select-window.html</id>
        <link href="https://selenium.dev/selenium-ide/blog/2018/12/05/the-difficulties-of-select-window.html">
        </link>
        <updated>2018-12-05T06:00:00Z</updated>
        <summary type="html"><![CDATA[<p>When recording a test case, more often than not, window management becomes an issue,
the test case may open a popup, or follow a <code>target=_blank</code> link.
Nonetheless, Selenium IDE is expected to follow, and record, recording the window and tab
switching in such a way, that there is no need for manual fixing post-recording.</p>
<p>But here lies the issue <strong>selecting windows is stateful</strong>.</p>
]]></summary>
        <author>
            <name>Tomer Steinfeld</name>
            <uri>https://twitter.com/corevous</uri>
        </author>
    </entry>
</feed>