From e5b5cdbf2b05a01402ae51dea7b02c012e9a6b6c Mon Sep 17 00:00:00 2001 From: Nathan Knowler Date: Fri, 10 Jul 2026 00:40:27 -0500 Subject: [PATCH] Update wording --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index a7a41b2..d985b04 100644 --- a/README.md +++ b/README.md @@ -27,7 +27,7 @@ Create your sectioned content how you normally would, except wrap with the custo By default, the element has an implicit `group` role similar to the `
` element, but is unnamed. It’s likely a good idea to leave it that way. -Generally, it’d be a good idea to bundle the custom element definition and load it in a parser/render blocking way to avoid any flash of unstyled custom element. That might go against your performance sensibilities, but consider the fact that built-in HTML elements are predefined before the body loads and there’s no flash of undefined `
` element. No need to hide the element and its contents until the definition — it’s semantically accessible and visually presentable without the enhancement of being a disclosure. +Generally, it’d be a good idea to bundle the custom element definition and load it in a parser/render blocking way to avoid any flash of unstyled custom element. That might go against your performance sensibilities, but consider the fact that built-in HTML elements are predefined before the body loads and there’s no flash of undefined `
` element. No need to hide the element and its contents until the definition — it’s semantically accessible and visually presentable without the enhancement of being a disclosure. Define early and avoid a host of problems. ## Styling -- 2.51.2