title: Google Chrome didn't render DOM in inactive mode?
body: <p>I have the following selenium script running in google chrome/chromedriver 90 in macOS, here is my finding: when running the script and make the chrome process active all the time, it works as my expectation. When running the script and switch to other unrelated process, just let the attaching chrome process alive in the inactive (not hidden) process state, it breaks!</p>
  <pre class="lang-py prettyprint-override"><code>the_element = self.waiter.until(EC.element_to_be_clickable((By.XPATH, '//div[@class=&quot;channel-area&quot;]')))
  
  try:
      the_element.click()
  except Exception as e:
      logger.exception(e)
      import pdb; pdb.set_trace()
  </code></pre>
  <p>Exception:</p>
  <pre><code>Message: element click intercepted: Element &lt;div class=&quot;channel-area&quot;&gt;...&lt;/div&gt; is not clickable at point (380, 623). Other element would receive the click: &lt;div class=&quot;leave-active&quot; style=&quot;z-index: 1034;&quot;&gt;&lt;/div&gt;
    (Session info: chrome=90.0.4430.212)
  </code></pre>
  <p>I think a web browser shouldn't expose the process state to a website/web developer, right? Is it a user state leak? Or are there any magic environment chrome flags to disable it?</p>
  <p>BTW, I've confirmed that firefox/firefox-esr 86 couldn't repro this issue, no custom configurations there.</p>