Manager not displayed in newer version of Chrome

[polnops]

When I start the manager and run it on a new version of Chrome (e.g. after 80.0), the manager fails to display (even though my servers still run correctly).

Reverting Chrome to v55.0 fixes the problem, but I'm just curious if anyone has successfully had the manager show up correctly in the newest version of Chrome?

[maffoo]

This is a known issue. Chrome 80 dropped support for html imports, which are needed by the polymer library used in scalabrad-web. Fixing this would require migrating to polymer v3, which is a pretty big chunk of work.

[jayich]

https://www.chromestatus.com/feature/5144752345317376

[gschaffner]

Hi @maffoo --- I'm attempting to gauge how much work this would entail and how feasible it would be for someone who is unfamiliar with Node (me) to take this on. So far, my working understanding is that the path would be something like

• Replicate a build of the current master and verify that it works on Chromium < 80.
• Upgrade from Polymer 1.6 to 2.0.
  • Get PolymerElements/{iron,neon,paper}-elements 2.0 as individual elements rather than as a pack. The {iron,neon,paper}-elements repos haven't been upgraded for Polymer 2.0. See here.
    • paper-menu ends with v1 and is deprecated in favor of paper-listbox. We need to migrate unless we want to just use the unmaintained fork Upgrades paper-menu to polymer2.0-preview in hybrid mode. Fixes #110 googlearchive/paper-menu#113.
  • Migrate from PolymerTS to PolymerDecorators. This might be partially automated: see Develop process and/or tool for upgrading to Polymer 2 and PolymerDecorators nippur72/PolymerTS#110.
  • ??
• Upgrade from Polymer 2.0 to 3.0.
  • This upgrade is mostly automated by Polymer modulizer.
  • ??

Does this look accurate to you? Any large steps that I'm missing in the ?? areas? Thanks!

[fanmingyu212]

A temporary workaround for chrome version > 80: karma-runner/karma#3419 (comment). I think this issue should still be addressed if possible though.

[xiaoyuejin]

Will this issue be further addressed?

[gschaffner]

I'm hoping to continue working on this, but I'm completely unfamiliar with web tech and was hoping for some advice from @maffoo before continuing.

Current progress is here.

[gschaffner]

@maffoo Are you working on this? I saw your new branch and wanted to make sure you'd seen this issue and this branch. If you are, it'd be great if you could push as you go as I'm interested in reading through the changes that are made to upgrade.

[xiaoyuejin]

Just wondering: Is anyone still trying to solve this issue? Actually, my question is, how to go around this problem? I mean there must be a way to do that. I can't imagine the entire google team is using an old version of Chrome on all the measurement computers...

[fanmingyu212]

@xiaoyuejin see the workaround above: #331 (comment). This still works for us.

[fanmingyu212]

It seems that HTMLImports was completely removed from chrome in version 88. The workaround above does not work anymore. The solution we use right now is to keep chrome up to date (it does not work with labrad), and install another chromium-based browser that is not updated so it would work with labrad.

[xiaoyuejin]

Yeah, that's exactly why I was asking the questions I asked above...