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

iron-icon does not work in Firefox #133

Open
1 of 8 tasks
nicolethenerd opened this issue Jan 22, 2019 · 2 comments
Open
1 of 8 tasks

iron-icon does not work in Firefox #133

nicolethenerd opened this issue Jan 22, 2019 · 2 comments

Comments

@nicolethenerd
Copy link

nicolethenerd commented Jan 22, 2019

Description

The demo at https://www.webcomponents.org/element/@polymer/iron-icon/demo/demo/index.html does not run in Firefox.

Expected outcome

The demo works in Firefox.

Actual outcome

The icons do not appear.

Live Demo

https://www.webcomponents.org/element/@polymer/iron-icon/demo/demo/index.html

Not sure if this is an instance of bug #122 ? I don't see anything in the console on the demo, but when I try to use an iron-icon in my own project, I get that error in FF - not sure if this is the same issue or something else.

Browsers Affected

  • Chrome
  • Firefox
  • Safari 9
  • Safari 8
  • Safari 7
  • Edge
  • IE 11
  • IE 10
@sunc9oa
Copy link

sunc9oa commented Aug 2, 2019

I got same issue when I use iron-icon element, it show Error: this._meta.byKey is not a function error message.
I try to import iron-meta before iron-icon and the issue be solved, but I don't why.

import { LitElement, html, css } from 'lit-element'

// import iron-meta element before iron-icon
import '@polymer/iron-meta/iron-meta.js'
import '@polymer/iron-icon/iron-icon.js'
import '@polymer/iron-icons/iron-icons.js'

class AppShell extends LitElement {
  render() {
    return html`
      <iron-icon icon="menu"></iron-icon>
    `
  }
}
customElements.define('app-shell', AppShell)

Hope this help.

@NickdeK
Copy link

NickdeK commented Feb 7, 2020

If you use the git repo instead of the npm repo in your package.json it also solves the problem. I think the authors just need to make a new release to solve this.

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

No branches or pull requests

3 participants