title: WaitUntil not waiting / Get HTML on WaitForSelectorAsync
body: <p>Having two problems that I would appreciate some advise on.  Have used puppeteer in the past in node, but for some reason, running into a problem on the sharp version. </p>
  
  <p>Basically I'm crawling a webpage with a WaitUntil set to  WaitUntilNavigation.Networkidle0, the longest wait period.  In my node code, this runs and loads my website correctly, but in the C# version, I get the page without angular loaded.  From the best I can tell it is not waiting and returning the initial Load state.  Below is my code.</p>
  
  <pre><code>        if (BROWSER == null)
          {
              await new BrowserFetcher().DownloadAsync(BrowserFetcher.DefaultRevision);
  
              BROWSER = await Puppeteer.LaunchAsync(new LaunchOptions
              {
                  Headless = true,
                  Args = new string[] { "--no-sandbox", "--disable-accelerated-2d-canvas", "--disable-gpu", "--proxy-server='direct://'", "--proxy-bypass-list=*" }
              });
          }
  
          if (page == null)
          {
              page = await BROWSER.NewPageAsync();
              await page.SetUserAgentAsync("PScraper-SiteCrawler");
              await page.SetViewportAsync(new ViewPortOptions() { Width = 1024, Height = 842 });
  
              var response = await page.GoToAsync(url, new NavigationOptions() { Referer = "PScraper-SiteCrawler", Timeout = timeoutMilliseconds, WaitUntil = new[] { WaitUntilNavigation.Networkidle0 } });
          }
  </code></pre>
  
  <p>Timeout is set to 30 seconds, or 30,000 milliseconds.  I then get the html of the page doing</p>
  
  <pre><code>await reponse.TextAsync()
  </code></pre>
  
  <p>My second question is unrelated, but likely simpler to solve.  One route I was considering was using the page.WaitForSelectorAsync() method.  This appears to wait until the content I'm looking for is loaded, but I haven't been able to figure out how to get the entire html of the page after this is done from the ElementHandle return.</p>
  
  <p>Would appreciate some help here, tried a couple routes and haven't been able to figure out whats causing the difference between the node and C# code.  </p>