-
-
Notifications
You must be signed in to change notification settings - Fork 17
/
Copy pathindex.html
904 lines (683 loc) · 27 KB
/
index.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
<!doctype html>
<html lang=en>
<title>snuggsiツ</title>
<meta charset=utf-8>
<meta
name=viewport
content=user-scalable=no,initial-scale=1.0,minimum-scale=1.0,maximum-scale=1.0,width=device-width,height=device-height
>
<link rel=icon href=/favicon.ico >
<link
as=style
href=index.css
rel='preload stylesheet'
>
<!--
<link
as=fetch
rel=preload
type=text/html
id=github-ribbon
href=/examples/github-ribbon
>
<link
as=fetch
rel=preload
id=header-group
href=/examples/header-group>
-->
<style>
// enough inline styles to paint to fold
// Japanese colors - https://en.wikipedia.org/wiki/Traditional_colors_of_Japan#Red.2FViolet_series
</style>
<script src=https://unpkg.com/snuggsi></script>
<!-- https://developer.mozilla.org/en-US/docs/Web/HTML/Element/base -->
<!-- https://www.speedshop.co/2015/10/21/hacking-head-tags-for-speed-and-profit.html -->
<base href=https://snuggsi.com>
<body role=application>
<github-ribbon style=display:none
url=https://github.com/devpunks/snuggsi>
</github-ribbon>
<header-group style=text-align:center;padding-top:1em;display:block>
<h2>
<a href=//snuggsi.com title=snuggsiツ style=color:white>snuggsiツ</a>
<br>
<small>Easy Custom Elements in
<a
target=github
href=https://github.com/devpunks/snuggsi/tree/main/dist#readme>
~ 1<abbr title=kiloByte>kB</abbr>
</a>
</small>
</h2>
<section slot=subheader id=badges >
<a href=https://npmjs.org/package/snuggsi>
<img alt='NPM monthly downloads' src=https://img.shields.io/npm/dm/snuggsi.svg?style=flat>
</a>
<a href=http://github.com/devpunks/snuggsi/tree/master/dist#readme>
<img alt='Brotli size' src=https://img.shields.io/badge/Brotli%20size:-~%201kB-ff69b4.svg>
</a>
<a href=http://npmjs.com/package/snuggsi>
<img alt='npm version' src=http://img.shields.io/npm/v/snuggsi.svg>
</a>
<a href=http://github.com/devpunks/snuggsi/blob/master/LICENSE.txt target=external>
<img alt=license src=http://img.shields.io/npm/l/snuggsi.svg>
</a>
<a href=http://github.com/devpunks/snuggsi/issues target=external>
<img alt='Pull requests welcome!' src=http://img.shields.io/badge/PRs-welcome-brightgreen.svg>
</a>
</section>
</header-group>
<nav>
<!-- https://vuejs.org/v2/guide -->
<!-- http://aurelia.io/consulting.html -->
<!-- https://skatejs.gitbooks.io/skatejs/content -->
<header>Getting Started</header>
<ul>
<li>
<details>
<summary><a href=#installation>Installation</a></summary>
<ul>
<li>
<a href=#>Files Organization</a>
<!-- https://medium.com/styled-components/component-folder-pattern-ee42df37ec68 -->
<li hidden >
<a href=#><code><script></code> tag</a>
<li hidden >
<a href=#>Chrome Extension</a>
<!-- https://github.com/pakastin/redom-devtools/blob/master/dist/devtools.js -->
<li hidden >
<a href=#><code>$ npm i snuggsi</code></a>
</ul>
</details>
<li>
<details>
<summary><a href=#lifecycle >Lifecycle</a></summary>
<ol>
<li>
<a href=#lifecyle:definition >Definition</a>
<li>
<a href=#lifecyle:construction >Construction</a>
<li>
<a href=#lifecyle:reflection >Reflection</a>
<li>
<a href=#lifecyle:imports >Imports</a>
<!-- This is a bit wonky in nomenclature and semantics -->
<li>
<a href=#lifecyle:slots >Slot Replacement</a>
<li>
<a href=#lifecyle:rendering >Rendering</a>
<ol>
<li>
<a href=#lifecycle:rendering:tokens >Tokens</a>
<li>
<a href=#lifecycle:rendering:templates >Templates</a>
<li>
<a href=#lifecycle:rendering:registration >Event Registration</a>
</ol>
<li>
<a href=#lifecyle:idle >Idle</a>
<li>
<a href=#lifecyle:events >Handling Events</a>
</ol>
</details>
<li>
<details>
<summary><a href=#conventions >Conventions</a></summary>
<ul>
<li>
<a href=#tokens >Tokens</a>
<li>
<!-- http://blog.aurelia.io/2016/05/23/aurelia-shadow-dom-v1-slots-prerelease -->
<a href=#slots >Slots</a>
<li>
<a title=Context href=#context >Context</a>
<li>
<a title=Mixins href=#mixins >Mixins</a>
</ul>
</details>
<li>
<details>
<summary><a href=#practices>Best Practices</a></summary>
<ul>
<li></li>
</ul>
</details>
<li>
<details>
<summary><a href=#antipatterns>Anti-Patterns</a></summary>
<ul>
<li>Javascript Attributes</li>
<!-- No javascript in `<link>` elements (think <LINK> headers -->
</ul>
</details>
</ul>
<header>Documentation</header>
<ul>
<li>
<details>
<summary><a href=#interfaces>Interfaces</a></summary>
<ul>
<li>
<details>
<summary><a href=#interfaces:element>Element</a></summary>
<ul>
<li>
<a href=#interfaces:element:select>.select</a>
<li>
<a href=#interfaces:element:selectAll>.selectAll</a>
</details>
<li>
<a href=#interfaces:template>Template</a>
</ul>
</details>
<li>
<details>
<summary><a href=#events>Events</a></summary>
<ul>
<li>
<a href=#events:connect><em>(on)</em>connect</a>
<li>
<a href=#events:idle><em>(on)</em>idle</a>
<li>
<a
rel=external
target=external
href=https://developer.mozilla.org/en-US/docs/Web/API/GlobalEventHandlers>Native Handlers</a>
</ul>
<footer>
<ul>
<li>
<a
rel=help
target=wikipedia
href=https://en.wikipedia.org/wiki/DOM_events#Inline_model >
Inline Registration
</a>
</ul>
</footer>
</details>
<li>
<details>
<summary><a href=#mixins>Mixins</a></summary>
<footer>
<ul>
<li>
<a
target=mdn
rel=external
href=https://developer.mozilla.org/en-US/docs/Glossary/Mixin>
<abbr title='Mozilla Developer Network'>MDN</abbr>
Mixins
</a>
<li>
<a
rel=external
target=wikipedia
href=https://en.wikipedia.org/wiki/Mixin>
Wikipedia Mixins
</a>
<li>
<a
target=mdn
rel=external
href=https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Classes#Mix-ins>
ECMAScript Mixins
</a>
</ul>
</footer>
</details>
<li>
<details>
<summary><a href=#modules>Modules</a></summary>
<ul>
<li>
<a href=#modules:html><abbr title='Hyper-Text Markup Language'>HTML</abbr> Modules</a>
<li>
<a href=#modules:ecmascript>ECMAScript Modules</a>
</ul>
<footer>
<ul>
<li>
<a rel=external target=external href=https://aremodulesready.com>Are Modules Ready?</a>
</ul>
</footer>
</details>
<li>
<details>
<summary><a href=#imports>Preloads</a></summary>
<!-- meta tags -->
<!-- link rel=preload/prefetch -->
<!-- HTML5 The road to link relations -->
<!-- https://en.wikipedia.org/wiki/Link_relation -->
<!-- resource hints https://w3c.github.io/resource-hints/ -->
<!-- link types - https://html.spec.whatwg.org/multipage/links.html#linkTypes -->
<footer>
<ul>
<li>
<a
target=ietf
rel=external
title='View Web Linking on IETF'
href=https://tools.ietf.org/html/rfc5988>
<abbr title='Internet Engineering Task Force'>IETF</abbr>
Web Linking
</a>
<li>
<a
rel=external
target=whatwg
title='View Link Relations on WHATWG'
href=https://blog.whatwg.org/the-road-to-html-5-link-relations>
<abbr title='Web Hypertext Application Technology Working Group'>WHATWG</abbr>
Link Relations
</a>
<li>
<a
target=mdn
rel=external
title='View Preloading Content on MDN'
href=https://developer.mozilla.org/en-US/docs/Web/HTML/Preloading_content>
<abbr title='MDN'>MDN</abbr>
Preloading Content
</a>
</ul>
</footer>
</details>
</ul>
</nav>
<main id=content>
<section view id=installation>
<h1>Easy Installation</h1>
<p>No need for Node.js, Webpack, Babel, or Gulp.
<p><strong>snuggsiツ</strong> works in production or in a plain 'ol HTML file!
<p>Simply place the following script within your webpage:</p>
<pre><code>
<script src=https://unpkg.com/snuggsi></script>
</pre></code>
<p class=center>Et Voila <em>(that's it!)</em> ツ
<p class=center>See
<a target=github href=https://github.com/devpunks/snuggsi/wiki/Module-Imports>ECMAScript Module Imports</a>
for<code> <script type=module></code> support!
</section>
<section view id=lifecycle>
<h1>Custom Element Lifecycle</h1>
<dl>
<dt id=lifecycle:definition >0. <code>define</code> Element
<dd>
A custom element is <em>"defined"</em> by specifying the <code>Element `your-tag-name`</code>
declaration immediately followed with a <code>(class extends HTMLElement {})</code> definition.
The custom element will be considered an <code>UnknownHTMLElement</code> until an <code>Element</code>
definition is specified. This means your custom element can be styled like any other HTML element.
However, your element will not have functionality until after definition.
<dt id=lifecycle:construction >1. <code>initialize</code> Construction
<dd>
After <strong>Definition & Declaration</strong> the custom element will go through
it's <code>constructor ()</code> routine. Typically you will not need to define a
<code>constructor ()</code> on your <code>class</code>. <strong>snuggsiツ</strong>
takes care of all <code>super ()</code> calls for you on instantiation.
<br><br>
If you would like to alter the custom element construction,
define an <code>initialize ()</code> function which is a hook that will be used automatically.
<dt id=lifecycle:reflection >2. Reflection
<dd>
After <strong>Construction</strong> the custom element will inspect your
<code>class extends HTMLElement</code> definition for Event Handlers.
These are typically methods prefixed with <em><strong>on</strong> (example: <code>onclick (event)</code>)</em>.
<strong>snuggsiツ</strong> will <em>automagically<sup>™</sup></em>
delegate the event handler to your custom element container. As a
convenience the <code>this</code> keyword will <strong><em>Always</em></strong> be bound to the custom element.
<dt id=lifecycle:imports >3. <code><link></code>Importing
<dd>
The <code><link rel=import></code> step is critical for custom elements which contain a definition within an external file.
<em>(See <a
target=webcomponents
rel=external
href=https://www.webcomponents.org/community/articles/introduction-to-html-imports>
HTML Imports
</a> for more detail)</em>.
This is not your typical <em>"import javascript library"</em> you have been used to for years.
Imports are relative to the partial HTML document that contains the contents to hydrate each
instance of your custom element on upgrade.
<dt id=lifecycle:slots >4. <code><slot></code> Replacement
<dd>
After <strong>Importing</strong> the default contents of your custom element
there will be a replacement of any child elements with a
<code><a
target=mdn
rel=external
href=https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/slot>slot=slotname</a></code>
attribute within your custom element. Your <strong><em>"Named Slot Elements"</em></strong>
will replace the default import slots If the <em>slot</em> attribute coincides with
a <code><a target=mdn rel=external href=https://developer.mozilla.org/en-US/docs/Web/HTML/Element/slot><slot name=slotname></a></code>
defined within the imported custom element. In other words …
An element with a slot attribute is assigned to the slot created by the
<slot> element whose name attribute's value matches that slot attribute's value.
<dt id=lifecycle:rendering >5. Rendering
<dd>
Rendering of your custom element occurs on <strong>three specific occasions</strong>:
<ol>
<li>After <strong>on</strong> events <em>(example: <code>onclick (event)</code>)</em>.
<li>After initial <code>onconnect ()</code> hook is fired.
<li>Explicit calls to <code>this.render ()</code>.
</ol>
<em>(See <a
target=mdn
rel=external
href=https://developer.mozilla.org/en-US/docs/Web/API/window/requestAnimationFrame>
Animation Frames
</a> for more detail)</em>. Rendering can be disabled from within event handlers by calling <code>event.prevent ()</code>
from within handler functions. <strong>Be sure to declare <code>event</code> in your method signature.</strong>
<em>(example: <code>onclick (event) { event.prevent () }</code></em>
<dt id=lifecycle:rendering:tokens >5a. <code>{token}</code> Binding
<dd>
Occurs by <strong><em>"Tree Walking"<sup>™</sup></em></strong>
child content of your custom element each time a <code>{token}</code> is discovered.
Tokens are a declarative placeholder for <strong><em>"Computed Property"</em></strong> values declared in your class definition.
<code>{foo}</code> is replaced with <code>"some value"</code> If a <code>get foo () { return 'some value' }</code>
is a property of your class definition.
<dt id=lifecycle:rendering:templates >5b. <code><template></code> Iteration
<dd>
Often we need to iterate over collections within a custom element. Traditionally this is done
<a
target=external
rel=external
href=https://tylermcginnis.com/imperative-vs-declarative-programming/>imperatively vs. declaratively</a>
by using looping mechanisms that feel more like leaky abstractions than common HTML. <strong>snuggsiツ</strong>
will <strong><em>"Tree Walk"<sup>™</sup></em></strong> the children of your custom element looking for
<code><template name=…></code> and <em>"bind"</em> the collection value of a property with the same name on your class.
<dt id=lifecycle:rendering:registration >5c. Event Registration
<dd>
One of the many pains of classic browser programming is registering events on DOM elements.
<strong>Event Registration</strong> is the process of declaratively registering event handlers by name
within your custom element and <code><template></code> HTML.
<strong>snuggsiツ</strong> will <strong><em>"Tree Walk"<sup>™</sup></em></strong>
your custom element and children looking for
<a
rel=help
target=mdn
href=https://developer.mozilla.org/en-US/docs/Web/API/GlobalEventHandlers>valid W3C GlobalEventHandlers</a>
by name once <em>"connected"</em> to the HTML document.
<code><foo-bar onclick=hello></code> will <em>"automagically"<sup>™</sup></em> register
the <code>hello (event) { }</code> handler defined on the custom element <code>class</code> definition.
<dt id=lifecycle:idle >6. Post-Render Idle
<dd>
Idling occurs after the <strong>Rendering</strong> routine consisting of
<strong>Token Binding</strong>, <strong>Template Iteration</strong>,
& <strong>Event Registration</strong> has completed. This
<a
target=wikipedia
rel=external
href=https://en.wikipedia.org/wiki/Frame_rate#Modern_video_standards>
16<abbr title=Millisecond>ms</abbr>
</a>, or
<a
target=quora
rel=external
href=https://www.quora.com/What-is-60-frames-per-second>
60 Frames Per Second
</a> rate period coincides with the
<a
target=mdn
rel=external
href=https://developer.mozilla.org/en-US/docs/Web/API/Window/requestIdleCallback>
idle time between animation frames
</a>.
<dt id=lifecycle:events >7. Triggering Events <em>(On completion repeats rendering step #5 a, b, & c)</em>
<dd>
There are a few ways events are registered by <strong>snuggsiツ</strong>.
Whether you choose a declarative registration <code><button onclick=onfoo></code>,
an imperative registration <code>onclick (event) {}</code>,
or an explicit registration <code>this.on ('click', this.onfoo)</code>,
the <strong>Rendering</strong> pipeline will force a
<a target=external rel=help href=https://www.phpied.com/rendering-repaint-reflowrelayout-restyle/>
<em>"reflow"</em> and <em>"repaint"</em>
</a> unless the <code>event</code> is explicitly prevented.
<p class=center><br>
<em>To prevent <strong>Rendering</strong> simply prevent the default event action by calling <br>
<code>event.prevent ()</code> within the custom element handler.</em>
</section>
<section view id=conventions>
<h1>Conventions</h1>
<article><!-- <medium-article> -->
<h2>Child Selection</h2>
<p> Here is where conventions on selecting children will live.
<header>Selecting a <strong>Single</strong> Child</header>
<code>Element.select (<em>selector</em>)</code>
<p>This is text about Element.select
<header>Selecting <strong>Multiple</strong> Childen</header>
<code>Element.selectAll (<em>selector</em>)</code>
<p>This is text about Element.selectAll
<aside>
<header>Relatd Links</header>
<ul>
<li>
<a rel=help target=external href=#>
Element.querySelector ()
</a>
<li>
<a rel=help target=external href=#>
Element.querySelectorAll ()
</a>
</aside>
</footer>Medium Article Link</footer>
</article>
<!--
<header>Creating Custom Elements</header>
<header>Default Content</header>
<header>Styling Real Estate</header>
<header>Registering Events</header>
<header>Looping Over Collections</header>
<header>The Data Context</header>
<header>Reusable Components</header>
<header>When to separate</header>
<header>Importing HTML "Partials"</header>
https://www.scirra.com/blog/ashley/34/html-imports-are-the-best-web-component
<header><em>Prefetching</em> <code><link></code>s</header>
$$$$$ https://www.youtube.com/watch?v=tKvNeNGmOtU
<header><em>Preloading</em> Dependencies</header>
https://developer.mozilla.org/en-US/docs/Web/HTML/Link_types
https://developer.mozilla.org/en-US/docs/Web/HTML/Preloading_content
<header><em>Pagination</em> Dependencies</header>
https://yoast.com/rel-next-prev-paginated-archives
-->
<article><!-- <medium-article> -->
<header>The <abbr title='Push, Render, Precache, Lazy-load'>P.R.P.L.</abbr> Pattern</header>
<p>PRPL is a pattern for structuring and serving Progressive Web Apps (PWAs), with an emphasis on the performance of app delivery and launch. It stands for:
<ul>
<li><strong>P</strong>ush critical resources for the initial URL route.
Render initial route.
Pre-cache remaining routes.
Lazy-load and create remaining routes on demand.
<p>Beyond targeting the fundamental goals and standards of <abbr title='Progressive Web Apps'>P.W.A.</abbr>s, <abbr title='Push, Render, Precache, Lazy-load'>P.R.P.L.</abbr> strives to optimize for:
<ul>
<li> Minimum time-to-interactive
<ul>
<li>Especially on first use (regardless of entry point)
<li>Especially on real-world mobile devices
</ul>
<li>Maximum caching efficiency, especially over time as updates are released
<li>Simplicity of development and deployment
<p><abbr title='Push, Render, Precache, Lazy-load'>P.R.P.L.</abbr> is inspired by a suite of modern web platform features, but it’s possible to apply the pattern without hitting every letter in the acronym or using every feature.
<aside>
<header>Relatd Links</header>
<ul>
<li>
<a rel=help target=external href=https://www.youtube.com/watch?v=4bZvq3nodf4>
Progressive Performance <em>(Chrome Dev Summit)</em>
</a>
<li>
<a rel=help target=external href=https://developers.google.com/web/fundamentals/performance/prpl-pattern/>
<abbr title='Push, Render, Precache, Lazy-load'>P.R.P.L.</abbr> Pattern
</a>
<li>
<a rel=help target=external href=https://www.slideshare.net/grgur/prpl-pattern-with-webpack-and-react>
<abbr title='Push, Render, Precache, Lazy-load'>P.R.P.L.</abbr> Pattern with Webpack and React
</a>
<li>
<a rel=help target=external href=https://news.ycombinator.com/item?id=13751466>
Responses to <abbr title='Push, Render, Precache, Lazy-load'>P.R.P.L.</abbr> Pattern
</a>
</aside>
</footer>Medium Article Link</footer>
</article>
<header>Bundling & Transpilation</header>
</section>
<section view id=antipatterns>
<h1>Anti-Patterns</h1>
<article>
<header>Talking to Strangers</header>
<p>
Should never reach outside of your component to talk to siblings.
There should be a "parent container" component that "sandboxes" in related components.
<footer></footer>
</article>
<article>
<header>Doing more than 16<abbr title=Milliseconds>ms</abbr> of Work</header>
<footer></footer>
</article>
<article>
<header>Unnecessary Reflow</header>
<footer></footer>
</article>
<article>
<header>Unnecessary Repaint</header>
<footer></footer>
</article>
</section>
<section view id=interfaces>
<h1>Interfaces</h1>
<p>This is some content about interfaces
<section id=interfaces:element>
<header><code>Element</code></header>
<p>Documentation about interfaces:element
<section id=interfaces:element:select>
<header><code>Element.select</code></header>
<p>Documentation about interfaces:element:select
<footer>This is the footer</footer>
</section>
<section id=interfaces:element:selectAll>
<header><code>Element.selectAll</code></header>
<p>Documentation about interfaces:element:select
<footer>This is the footer</footer>
</section>
</section>
</section>
<section view id=events>
<h1>Events</h1>
</section>
<section view id=tokens>
<h1>Tokens</h1>
</section>
<section view id=slots>
<h1>Slots</h1>
</section>
<section view id=context>
<h1>Context</h1>
</section>
<section view id=mixins>
<h1>Mixins</h1>
<h3>Further Learning</h3>
<ul>
<li>
<a href=/mixins><mixins></a>
<li>
<a
rel=help
target=wikipedia
href=https://en.wikipedia.org/wiki/Mixin>Mixin: Object Oriented Programing Concepts</a>
<li>
<a
rel=help
target=mdn
href=https://developer.mozilla.org/en-US/docs/Glossary/Mixin>Mix-in Definition</a>
<li>
<a
rel=help
target=mdn
href=https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Classes#Mix-ins>Class Mix-ins</a>
</ul>
</section>
</main>
<aside>
<header>Examples</header>
<details>
<summary><a title='<template>' href=/examples#template><template></a></summary>
<nav>
<ul>
<li>
<a title=Collections href=examples#template:collections>Collections</a>
<li>
<a title=Collections href=examples#template:object>Object</a>
</ul>
</nav>
</details>
<details>
<summary><a href=/examples#html><custom-elements></a></summary>
<nav>
<ul>
<li>
<a href=/examples/hello-world><hello-world></a>
<li>
<a href=/examples/header-group/example.html><header-group></a>
<li>
<a href=/examples/github-ribbon/example.html><github-ribbon></a>
<li>
<a href=/examples/add-subtract><add-subtract></a>
<li>
<a href=/examples/input-output.html><input-output></a>
<li>
<a href=/examples/to-do><to-do></a>
<li>
<a href=/examples/multiple-choice><multiple-choice></a>
<li>
<a href=/examples/infinity-calendar><infinity-calendar></a>
<li>
<a href=/examples/nav-view/example.html><nav-view></a>
<li>
<a href=/examples/user-list><user-list></a>
<li>
<a href=/examples/fidget-spinner><fidget-spinner></a>
</ul>
</nav>
</details>
<details>
<summary><a href=/examples#polyfills><polyfills-></a></summary>
<nav>
<ul>
<li>
<a href=/examples/datalist-><datalist-></a>
</ul>
</nav>
</details>
<details>
<summary><a title=Mixins href=/examples#mixins>Mixins ()</a></summary>
<nav>
<ul>
<li>
<a
title=Validate
href=#mixins:validate >
Validate
</a>
<li>
<!-- https://w3c.github.io/web-animations/#use-cases -->
<!-- https://discourse.wicg.io/t/proposal-wait-for-element-to-transition/2225 -->
<!-- https://medium.com/@adaptivepath/jedi-principles-of-ui-animation-2b88423b1dac -->
<!-- https://hackernoon.com/how-to-create-fancy-revealing-animations-with-these-simple-css-tricks-5b34614ae69a -->
<a title=Animate href=#>Animate</a>
<li>
<a title=Worker href=#>Worker</a>
<li>
<!-- https://www.smashingmagazine.com/2017/09/guide-virtual-reality-web-developers/?utm_source=frontendfocus&utm_medium=email -->
<a href=#>
<abbr title='Virtual Reality'>VR</abbr> <em>(Virtual Reality)</em>
</a>
</ul>
</nav>
</details>
</aside>
<footer role=contentinfo>
<header><a title=snuggsiツ href=/>snuggsiツ</a></header>
<em>Copyright © 2017-2025 A <strong><a rel=external target=devpunks title=devPunks href=//github.com/devpunks>devPunks</a></strong> project</em>
</footer>