issues
search
mfreed7
/
declarative-shadow-dom
Declarative Shadow DOM feature development
192
stars
9
forks
source link
issues
Newest
Newest
Most commented
Recently updated
Oldest
Least commented
Least recently updated
Simple Polyfill for setInnerHTML is wrong, cause dom parser also has "head"
#23
jogibear9988
closed
8 months ago
2
Add `HTMLLinkElement.prototype.use` to handle `adoptedStylesheets`
#22
mantou132
closed
1 year ago
2
Typos in # Feature Detection and Polyfilling
#21
estherbrunner
closed
1 year ago
0
Fix typo
#19
bennypowers
closed
1 year ago
1
Bring back HTML Imports using link
#18
vricop
opened
2 years ago
0
Shadow DOM streaming issue
#17
YusakuNo1
closed
2 years ago
2
Based on the clock example I made a quick polyfill (not complete as light-DOM slots are not supported)
#16
LionsAd
opened
2 years ago
1
Mutation observability
#15
bathos
closed
2 years ago
8
Add CSS property
#14
ByteEater-pl
closed
2 years ago
1
declaritive shadowroot inside an template
#13
chris-kruining
closed
3 years ago
7
Usage with Certain Built-In Elements
#12
michaelcpuckett
closed
3 years ago
4
Support for addEventListener
#11
dpnishant
closed
3 years ago
1
This is literally the best Web Components feature since sliced cheese.
#10
JoshuaWise
closed
3 years ago
1
getInnerHTML shouldn't distinguish between open and closed
#9
annevk
opened
4 years ago
8
Performance compared to custom element solution
#8
drdreo
closed
3 years ago
3
Experimental Chrome implementation not working when rendered from React
#7
steobrien
closed
4 years ago
3
Intersection semantics with Scoped Registries
#6
caridy
closed
4 years ago
4
Interaction with disabledFeatures
#5
annevk
closed
3 years ago
3
Multiple declarative shadow roots inside a single host
#4
rictic
closed
3 years ago
5
supportsDeclarativeShadowDOM returns true for current non-implementing browsers
#3
rictic
closed
4 years ago
5
Attribute names should not contain underscores
#2
domenic
closed
4 years ago
1
Consider using a separate tag
#1
koto
closed
4 years ago
3