A <tabs-panel /> accepts contents for two slots, named "tab" and "content". The tabs are shown spaced out and clickable, controlling their associated content.
Critique or comments welcome.
[...]
On Monday, July 10, 2023 at 9:23:09 PM UTC-5, luserdroog wrote:
A <tabs-panel /> accepts contents for two slots, named "tab" and "content". The tabs are shown spaced out and clickable, controlling their associated content.
Critique or comments welcome.
[...]
You can leverage <details /> for this too. Something like:
On Tuesday, July 11, 2023 at 12:40:30 AM UTC-5, Michael Haufe (TNO) wrote:
On Monday, July 10, 2023 at 9:23:09 PM UTC-5, luserdroog wrote:
A <tabs-panel /> accepts contents for two slots, named "tab" and "content". The tabs are shown spaced out and clickable, controlling their associated content.
Critique or comments welcome.
[...]
You can leverage <details /> for this too. Something like:
That's pretty cool. <defensive reaction>I think there are real advantages
of abstraction, encapsulation, and packaging with the web component approach. All the functionality is wrapped up in the component.
The application doesn't have to do a thing beyond constructing the html. </defensive reaction>
The clickable words should probably be <button>s for accessibility.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 469 |
Nodes: | 16 (2 / 14) |
Uptime: | 44:32:37 |
Calls: | 9,449 |
Calls today: | 6 |
Files: | 13,596 |
Messages: | 6,111,945 |
Posted today: | 1 |