[
https://issues.apache.org/jira/browse/KUDU-3402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17736498#comment-17736498
]
Zoltan Martonka commented on KUDU-3402:
---------------------------------------
I looked at the new repo and merged the changes. However the problem is still
present. It uses polymer 1.x, which is not updated for 4 years (3.x is the
current version). Updating to a newer mayor version polymer is far from trivial.
Also there is an open issue:
[https://github.com/catapult-project/catapult/issues/2489]
Although at first glance the project is maintained, it seems the trace-viewer
not running on chrome and Firefox for 4 years is a known and ignored issue.
> Make tracing.html work on newer browsers
> ----------------------------------------
>
> Key: KUDU-3402
> URL: https://issues.apache.org/jira/browse/KUDU-3402
> Project: Kudu
> Issue Type: Improvement
> Reporter: Marton Greber
> Priority: Minor
>
> After starting up Kudu, navigate to one of the Master or Tablet Server
> /tracing.html endpoint to see the tracing web UI. By using a recent version
> of Chrome, one gets a blank screen. Pulling up the logs, one can see the root
> cause: document.registerElement:
> {code:java}
> Uncaught TypeError: document.registerElement is not a function
> at tracing.js:31:88
> at tracing.js:31:448 {code}
> By checking the [MDN Web
> Docs|https://developer.mozilla.org/en-US/docs/Web/API/Document/registerElement],
> it can be seen, that this feature has been deprecated. In Chrome it was
> removed in version 80.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
