diff --git a/.tool-versions b/.tool-versions
new file mode 100644
index 0000000..a5a47f9
--- /dev/null
+++ b/.tool-versions
@@ -0,0 +1 @@
+nodejs 22.3.0
diff --git a/README.md b/README.md
index 09354f6..62103ab 100644
--- a/README.md
+++ b/README.md
@@ -41,6 +41,7 @@ If none of the tabs have `aria-selected=true`, then the first tab will be select
+```
### Events
@@ -109,6 +110,7 @@ In those cases, apply `data-tab-container-no-tabstop` to the `tabpanel` element.
### Unmanaged slots
`` aims to simplify complex markup away in the ShadowDOM, so that the HTML you end up writing is overall less. However sometimes it can be useful to have _full_ control over the markup. Each of the `::part` selectors are also ``s, this means you can take any part and slot it, overriding the built-in ShadowDOM.
+
#### Unmanaged `tablist`
You are able to provide your own `role=tablist` and `` will accommodate. This can be useful if you need extra presentational markup in the tablist. But remember:
@@ -148,6 +150,7 @@ You are able to slot the `tablist-tab-wrapper` part. This slot manages the tabs
```
+
#### Unmanaged `tablist-wrapper`
If you want to take full control over the entire tab region, including managing the content before and after the tabs, then you can slot the `tablist-wrapper` element. Bear in mind if you're supplying this element that:
diff --git a/custom-elements.json b/custom-elements.json
index 8355ce3..5772e8e 100644
--- a/custom-elements.json
+++ b/custom-elements.json
@@ -437,6 +437,9 @@
"kind": "field",
"name": "#tabList",
"privacy": "private",
+ "type": {
+ "text": "HTMLElement"
+ },
"readonly": true
},
{
diff --git a/examples/index.html b/examples/index.html
index 12fc8e7..238e319 100644
--- a/examples/index.html
+++ b/examples/index.html
@@ -67,27 +67,6 @@
Horizontal (custom tablist and tablist-wrapper)
-
Horizontal (custom tablist and tablist-tab-wrapper)