<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Have you tried using a wait… in Product Forum</title>
    <link>https://community.blueprism.com/t5/Product-Forum/Handling-long-running-Javascript-on-a-web-application/m-p/75671#M28276</link>
    <description>Have you tried using a wait stage with the condition 'Parent Document Loaded' or 'Document Loaded'?</description>
    <pubDate>Tue, 26 Feb 2019 17:15:00 GMT</pubDate>
    <dc:creator>david.l.morris</dc:creator>
    <dc:date>2019-02-26T17:15:00Z</dc:date>
    <item>
      <title>Handling long running Javascript on a web application</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Handling-long-running-Javascript-on-a-web-application/m-p/75670#M28275</link>
      <description>Hi All,

I have been working on a JSP page where upon clicking on a link another sub page gets opens and takes some time to get responsive(a min or so) because of a long running Javascript. I found that the only way to identify if new page has became responsive is a scroll bar that appears on application once the page has completely loaded but is not something that can be spied.

Please suggest if without using any kind of static wait&amp;nbsp;we could use some method to judge if page has became responsive and ready to be worked upon as I need to click on a dropdown on the new page which doesn't works till the time page is non responding</description>
      <pubDate>Mon, 25 Feb 2019 20:42:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Handling-long-running-Javascript-on-a-web-application/m-p/75670#M28275</guid>
      <dc:creator>RaghavSapra1</dc:creator>
      <dc:date>2019-02-25T20:42:00Z</dc:date>
    </item>
    <item>
      <title>Have you tried using a wait…</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Handling-long-running-Javascript-on-a-web-application/m-p/75671#M28276</link>
      <description>Have you tried using a wait stage with the condition 'Parent Document Loaded' or 'Document Loaded'?</description>
      <pubDate>Tue, 26 Feb 2019 17:15:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Handling-long-running-Javascript-on-a-web-application/m-p/75671#M28276</guid>
      <dc:creator>david.l.morris</dc:creator>
      <dc:date>2019-02-26T17:15:00Z</dc:date>
    </item>
    <item>
      <title>You can also try to switch…</title>
      <link>https://community.blueprism.com/t5/Product-Forum/Handling-long-running-Javascript-on-a-web-application/m-p/75672#M28277</link>
      <description>You can also try to switch to different browser and then try to spy ?</description>
      <pubDate>Wed, 27 Feb 2019 16:37:00 GMT</pubDate>
      <guid>https://community.blueprism.com/t5/Product-Forum/Handling-long-running-Javascript-on-a-web-application/m-p/75672#M28277</guid>
      <dc:creator>NarayanShrawagi</dc:creator>
      <dc:date>2019-02-27T16:37:00Z</dc:date>
    </item>
  </channel>
</rss>

