[
https://issues.apache.org/jira/browse/KUDU-3123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17139490#comment-17139490
]
Grant Henke commented on KUDU-3123:
-----------------------------------
I worked around this by downloading a version on Chromium before the
compatibility break (pre version 80.x.xxxx.xxx).
Following this answer: https://superuser.com/a/987935
# I found version `Branch Base Position: 668245` is for Chromium version
`77.0.3823.0` on https://omahaproxy.appspot.com/.
# Then I found the mac zip download on
https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Mac/668265/
# I downloaded the `chrome-mac.zip` unzipped it and ran the Chromium.app. (I
did need to allow unidentified apps to run in the Mac "Security & Privacy"
Settings.
# In that version of Chromium tracing.html works as expected.
> tracing.html doesn't render on newer browsers
> ---------------------------------------------
>
> Key: KUDU-3123
> URL: https://issues.apache.org/jira/browse/KUDU-3123
> Project: Kudu
> Issue Type: Bug
> Components: ui
> Reporter: Andrew Wong
> Priority: Major
> Labels: supportability
>
> I tried opening the tracing.html page using Google Chrome Version
> 81.0.4044.138, and the page was blank. Upon inspecting, seems like Chrome no
> longer supports {{registerElement}}
> {code:java}
> tracing.js:31 Uncaught TypeError: document.registerElement is not a function
> at tracing.js:31
> at tracing.js:31 {code}
> This was reported to the Chromium project as
> [https://bugs.chromium.org/p/chromium/issues/detail?id=1036492], which has
> been closed. We should update the trace viewer version in thirdparty to
> include whatever fixes are necessary, since tracing is pretty valuable in a
> pinch.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
