-
Notifications
You must be signed in to change notification settings - Fork 12
Issues: Netflix/x-element
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Test transitions from differing value types for the same content binding.
#223
opened Nov 20, 2024 by
theengineear
Make interpolation of text-only tags more strict (e.g., “<textarea>”).
#219
opened Nov 20, 2024 by
theengineear
Discussion: Should we guard the case where
map indexes are non-unique
#218
opened Nov 20, 2024 by
klebba
Discussion: Should we re-write template engine tests to compare against native behavior?
#212
opened Nov 18, 2024 by
theengineear
Discussion: Should we remove “live” from the default template interface?
#208
opened Nov 15, 2024 by
theengineear
Discussion: Should default template engine allow literal property binding.
#203
opened Nov 10, 2024 by
theengineear
Discussion: What patterns should be allowed for attributes and properties.
#199
opened Nov 8, 2024 by
theengineear
Default template engine won't stamp elements unless they implement a blank template
#152
opened Nov 20, 2023 by
klebba
Consider support for custom “serialize” / “deserialize” logic in property block.
#149
opened Aug 18, 2023 by
theengineear
Consider support for custom “updaters” in default template engine.
#132
opened Mar 4, 2023 by
theengineear
Discussion: Allow interpolation in “style” and “script” tags for template engine.
#123
opened Nov 4, 2022 by
theengineear
Discussion: Enable support for event bindings in Template Engine.
#120
opened Nov 4, 2022 by
theengineear
Ensure x-element compatibility with Custom Elements Everywhere test suite
#106
opened Apr 7, 2022 by
klebba
2
ProTip!
Follow long discussions with comments:>50.