⚠️ 📖 DRAFT: <tag-complete> #117
Conversation
examples/email-recipients/index.html
Outdated
| <email-recipients> | ||
|
|
||
| <template name=recipients> | ||
| <address> |
There was a problem hiding this comment.
is address allowed to be email address, not just physical? TIL
There was a problem hiding this comment.
@brandondees. May want to ask @kurtcagle or @janz93 @mrbernnz
|
|
||
| </script> | ||
|
|
||
| <script src=/browser-sync.es></script> |
There was a problem hiding this comment.
what if we load this conditionally based on localhost?
There was a problem hiding this comment.
There was a problem hiding this comment.
ah, hadn't picked up on that. well played.
examples/email-recipients/style.css
Outdated
|
|
||
| email-recipients > address:hover, | ||
| email-recipients { | ||
| box-shadow: 0 0 0.28em rgba(40,40,40,0.8); |
There was a problem hiding this comment.
no spaces between rgba values?
There was a problem hiding this comment.
@brandondees i'm down with that
There was a problem hiding this comment.
@albertoponti @brandondees hit me with "Tsu"! f783911
|
@brandondees @kurtcagle name rechange to |
|
yeah generalize the names to what the component actually does, rather than the specific use case for it. be sure to list known use-cases in the documentation but I'm all for more generic components. |
|
a consumer can always wrap them in their own context-specific name at import time, btw |
|
@brandondees OR use an identifier |
|
no i mean |
<tag-complete>Inspiration drawn from @kurtcagle's tags. @kurtcagle if you can drop the codepen in the description that would be great. Also gives you the chance to catch up to speed with the lifecycle callbacks.
https://snuggsi.now.sh#lifecycle please give it a moment as there is a 30s warmup time with the free plan at https://now.sh
Coparable Examples
Demonstration