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

27 Open 83 Closed
27 Open 83 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

Element shadowRoot will not function if template function is not provided
#267 opened Feb 19, 2025 by klebba
Use bare module specifiers throughout tests to link to @netflix/x-test
#266 opened Feb 19, 2025 by klebba
Some demo example links only function when developing x-element
#265 opened Feb 19, 2025 by klebba
Neither connectedCallback nor disconnectedCallback should be called when re-mapping causes a shuffle.
#254 opened Feb 18, 2025 by theengineear
1
Document example of including SVG.
#251 opened Feb 15, 2025 by theengineear
Minor language tweaks to x-parser error language
#248 opened Feb 13, 2025 by klebba
1
Update README to include a canonical "Hello World" element example
#247 opened Feb 13, 2025 by klebba
Ship an eslint plugin to help with strict html parsing.
#244 opened Feb 8, 2025 by theengineear
7
Relax required engine versions in package.json
#243 opened Jan 31, 2025 by klebba
@klebba
Reject JS-y escapes in html strings.
#242 opened Dec 22, 2024 by theengineear
5
Remove support for CDATA sections in the default template engine.
#241 opened Dec 22, 2024 by theengineear
Remove support for <math> elements in default template engine.
#238 opened Dec 21, 2024 by theengineear
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
2
Discussion: Consider support for a “debug” mode?
#210 opened Nov 16, 2024 by theengineear
1
Default template engine should throw for literal property binding.
#203 opened Nov 10, 2024 by theengineear
3
Lock down attribute name and property name patterns.
#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
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
ProTip! Mix and match filters to narrow down what you’re looking for.