-
-
Notifications
You must be signed in to change notification settings - Fork 4.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
[Beta regression] this.elementId
is null in tagless component
#13627
Comments
Well, it seems unintentional, but the new behavior does seem logical. Why would something without an element have an elementId? Why do extra work to calculate an elementId when it isn't going to be used? Is this a large issue for your addons? |
Not a big deal, it is an easy fix. I will stop relying on it, but I wanted to raise this change. |
Thank you for reporting. I will check with others to see if we should bring it back or try and do a deprecation. I'm unsure how big of an issue it is for others though... |
Thank you again for reporting the issue. If we have significant reports of this in future releases we can revisit, but for now I'm going to close... |
Add me to list as missing this ability. Building in accessibility relationships in tagless components was much easier with it! |
was this fixed? |
Just for the record (for future reference), we can use |
In 2.6,
this.elementId
called from within a tagless component returned something likeember123
.In 2.7 the same call in 2.7.0-beta.0 returns
null
.Intended or a regression?
The text was updated successfully, but these errors were encountered: