Created attachment 1580062 [details] AbortController is not defined Description of problem: login cluster console with cluster-admin, and click "Monitoring -> Query Browser", error in page is: react-dom.production.min.js:13 Uncaught ReferenceError: AbortController is not defined at router.ts:1 at ha (react-dom.production.min.js:13) at react-dom.production.min.js:13 at c (scheduler.production.min.js:10) at p (scheduler.production.min.js:10) at MessagePort.M.port1.onmessage (scheduler.production.min.js:10) Version-Release number of selected component (if applicable): 4.2.0-0.ci-2019-06-12-231255 How reproducible: Always Steps to Reproduce: 1. login cluster console with cluster-admin, and click "Monitoring -> Query Browser" 2. 3. Actual results: "query-browser" page is blank, error see the description part Expected results: Able to view "query-browser" page Additional info: Blocks testing under "query-browser" page
Which browser and browser version are you using?
`AbortController` is supported on the browsers we support: https://caniuse.com/#search=AbortController We could add a polyfill, but that shouldn't be necessary.
I can't reproduce on latest Firefox, Chrome, or Safari.
(In reply to Samuel Padgett from comment #1) > Which browser and browser version are you using? Google Chrome Version 58.0.3029.81 (64-bit) Firefox 52.0.2 (64-bit) maybe the version is too low
I'm going to reopen to add a polyfill. The latest Firefox ESR should be fine, but this is easy enough to address in case a user is on an old version. Lowering the severity and removing test blocker, however.
Reopened. Polyfill that was added by https://github.com/openshift/console/pull/1775 introduced a regression.
Follow on fix for the polyfill error: https://github.com/openshift/console/pull/1807
*** Bug 1723682 has been marked as a duplicate of this bug. ***
Tested on Firefox 52.0.2, "query-browser" page could be loaded. But we meet another error BZ 1724010 payload: 4.2.0-0.nightly-2019-06-25-222454
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:2922