about summary refs log tree commit diff stats
diff options
context:
space:
mode:
authorMarkus Wüstenberg2024-06-06 12:01:16 +0200
committerMarkus Wüstenberg2024-06-06 12:01:16 +0200
commit0b85f722038e0cc6cc7b66b7d0a704d845b614db (patch)
treed986529c8f6cb462f61a1057f48f93230938a933
parentd55a223e8af294678f10126bff9057ec38d7d978 (diff)
downloadgomponents-0b85f722038e0cc6cc7b66b7d0a704d845b614db.tar.lz
gomponents-0b85f722038e0cc6cc7b66b7d0a704d845b614db.tar.zst
gomponents-0b85f722038e0cc6cc7b66b7d0a704d845b614db.zip
Fix readme
-rw-r--r--README.md11
1 files changed, 6 insertions, 5 deletions
diff --git a/README.md b/README.md
index ca84c7f..bef2fbf 100644
--- a/README.md
+++ b/README.md
@@ -146,9 +146,10 @@ For more complete examples, see [the examples directory](examples/).
 ### What's up with the specially named elements and attributes?
 
 Unfortunately, there are four main name clashes in HTML elements and attributes, so they need an `El` or `Attr` suffix,
-respectively, to be able to co-exist in the same package in Go:
+to be able to co-exist in the same package in Go. I've chosen one or the other based on what I think is the common usage.
+In either case, the less-used variant also exists in the codebase:
 
-- `data` (`DataEl`/`DataAttr`)
-- `form` (`FormEl`/`FormAttr`)
-- `style` (`StyleEl`/`StyleAttr`)
-- `title` (`TitleEl`/`TitleAttr`)
+- `data` (`DataEl`/`Data`, `DataAttr` also exists)
+- `form` (`Form`/`FormAttr`, `FormEl` also exists)
+- `style` (`StyleEl`/`Style`, `StyleAttr` also exists)
+- `title` (`TitleEl`/`Title`, `TitleAttr` also exists)