Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Chrome 65 could break some Polymer 1.x and 2.x websites #132

Closed
1 of 2 tasks
chosh31 opened this issue Dec 13, 2017 · 1 comment · Fixed by #137
Closed
1 of 2 tasks

Chrome 65 could break some Polymer 1.x and 2.x websites #132

chosh31 opened this issue Dec 13, 2017 · 1 comment · Fixed by #137

Comments

@chosh31
Copy link

chosh31 commented Dec 13, 2017

In Link: https://www.polymer-project.org/blog/2017-10-18-upcoming-changes

What you should do in the next month or two:

  • Ensure that you're running the latest 1.x or 2.x release (1.10.1 or newer for 1.x; 2.1.1 or newer for 2.x).
  • If you have any HTML imports that contain ordinary style tags—not wrapped in a custom-style element or inside a template—use a custom-style element instead, to ensure the styles are moved into the main document.

Did you have a second phase patch?

chosh31 added a commit to chosh31/iron-flex-layout that referenced this issue Dec 15, 2017
e111077 added a commit that referenced this issue Feb 9, 2018
Use custom-style elements instead of style elements for HTML imports (Fixes #132)
@kobleistvan
Copy link

Seems that even if the <style> tags are wrapped in tags, Chrome still gives warning in console regarding deprecation. Should it be ONLY , without <style> tags inside of them? Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants