-
Notifications
You must be signed in to change notification settings - Fork 102
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
Add tests for ability to work with customized built-ins #376
Comments
@franktopel hm that's interesting. I guess a strawman proposal would be to create an element like |
It seems Angular still does not handle the Maybe the test could include something like comparing the innerText of the extended button in the following demos: |
And it is still not working in Angular, I have tested https://stackblitz.com/edit/angular-dginkc |
I think this would be a tricky test to add because the |
What makes you think Safari likely will never support this? Also, does that mean that you only consider scenarios that are well supported by all major browsers? |
This comment from Safari is the best explanation I could find:
Yeah I think so. I feel weird asking a framework to do work to support a feature which another browser actively opposes. I think if all the browsers agreed to a feature, but just hadn't gotten around to implementing it yet, that would be a different scenario and it would make sense to have tests then. |
Check if frameworks are able to recognize the special meaning of the
is=""
-attribute, and that it cannot be handled like a traditional attribute when it comes to dynamic element creation.The text was updated successfully, but these errors were encountered: