-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Behaviors may not run registered
if legacy element is subclassed
#5567
Closed
dfreedm opened this issue
Jul 1, 2019
· 3 comments
· Fixed by boikovdv/polymer#1 · May be fixed by #5569
Closed
Behaviors may not run registered
if legacy element is subclassed
#5567
dfreedm opened this issue
Jul 1, 2019
· 3 comments
· Fixed by boikovdv/polymer#1 · May be fixed by #5569
Comments
This is caused by moving behavior processing to be more like 1.x, which happened in 3.2. |
dfreedm
added a commit
that referenced
this issue
Jul 9, 2019
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically closed after being marked stale. If you're still facing this problem with the above solution, please comment and we'll reopen! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Root cause of PolymerElements/iron-a11y-keys-behavior#93
In this scenario:
x-bar
will haveregistered
called on it, andx-foo
will not.This means that
fizz
will only be set onx-bar
, and not onx-foo
's class, which is causing the error in iron-a11y-keys-behavior.The text was updated successfully, but these errors were encountered: