tab.hasTabPermission indirectly triggers an access to browser.currentURI, which for lazy tab browsers causes an incorrect value to be cached. To avoid this, skip the call to hasTabPermission. Differential Revision: https://phabricator.services.mozilla.com/D106622