webcomponents / webcomponents/custom-elements-everywhere
More property tests: camelCase names and inherited accessors
Open
- Dominant language
- JavaScript
- Stars
- 1.3k
- Forks
- 108
- PR merge metrics
- No merged PRs in 30d
Description
I've seen some issues recently with camelCase property names not being supported. I think that additional test cases for this would help drive fixes for them.
I also saw some probably buggy framework code that only did an in-check for own properties on the prototype of the element. This would break in inheritance cases, so we should add tests for those.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.