New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 842179 link

Starred by 3 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug

Blocked on: View detail
issue 842174
issue 842181
issue 842185

Blocking:
issue 806159



Sign in to add a comment

Tracking bug for migrating infra to polymer 2

Project Member Reported by estaab@chromium.org, May 11 2018

Issue description

Infra has several old versions of polymer in https://cs.chromium.org/chromium/infra/appengine/third_party/npm_modules/

Polymer <2 support is being removed from Chrome and we will need to update all apps and delete these old versions.

This is a tracking bug for migrating infra apps. I'm putting it under Infra>Platform so it doesn't end up in the infra triage queue but it would be good to have a general UI component for this.
 

Comment 1 by estaab@chromium.org, May 11 2018

Blockedon: 842174
Blocking: 806159

Comment 2 by estaab@chromium.org, May 11 2018

Blockedon: 842181

Comment 3 by estaab@chromium.org, May 11 2018

Blockedon: 842185

Comment 4 by kochi@chromium.org, May 12 2018

Thanks for filing a bug for this.

A little background:
Polymer V1 (and before) is based on Shadow DOM V0 / Custom Elements V0 APIs,
which will be deprecated and removed some time next year (planned). If you are
not directly using those native APIs, Polymer may polyfill them and the app
can continue to work, but it's not guaranteed.

For API migration, this doc helps for Shadow DOM v0 to v1
https://hayato.io/2016/shadowdomv1/

For polymer upgrade, please refer to Polymer team's document:
https://www.polymer-project.org/2.0/docs/upgrade

Sign in to add a comment