Skip to content

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.

Sign up for GitHub

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

26 Open 65 Closed
26 Open 65 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Relocate default template engine from x-element.js to x-template.js
#226 opened Nov 26, 2024 by klebba
@theengineear
Test transitions from differing value types for the same content binding.
#223 opened Nov 20, 2024 by theengineear
Throw immediately for poor “map” input.
#222 opened Nov 20, 2024 by theengineear
Stop appending dummy comments at the end of templates.
#221 opened Nov 20, 2024 by theengineear
Remove support for deprecated “plaintext” tag.
#220 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
@theengineear
Discussion: should we rework or remove unsafeHTML and unsafeSVG
#216 opened Nov 20, 2024 by klebba
@theengineear
3
Discussion: Should we re-write template engine tests to compare against native behavior?
#212 opened Nov 18, 2024 by theengineear
Create doc/FORMS.md
#211 opened Nov 18, 2024 by klebba
1
Discussion: Consider support for a “debug” mode?
#210 opened Nov 16, 2024 by theengineear
1
Discussion: Should we remove “live” from the default template interface?
#208 opened Nov 15, 2024 by theengineear
Discussion: Should we allow a “Node” as content.
#207 opened Nov 15, 2024 by theengineear
2
Discussion: Should default template engine allow literal property binding.
#203 opened Nov 10, 2024 by theengineear
3
Discussion: What patterns should be allowed for attributes and properties.
#199 opened Nov 8, 2024 by theengineear
Publish contributing guidelines
#186 opened Aug 9, 2024 by klebba
@klebba
2
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
3
Consider adding Bundlephobia badges.
#114 opened Apr 15, 2022 by theengineear
2
Ensure x-element compatibility with Custom Elements Everywhere test suite
#106 opened Apr 7, 2022 by klebba
2
Support Form-Associated Custom Elements
#83 opened May 7, 2021 by theengineear
1
ready.js could deduplicate readystate listener by target
#65 opened Nov 23, 2020 by klebba
10
ProTip! Mix and match filters to narrow down what you’re looking for.