From e6b21e295cfc700710e223cb16c0254c675e7ef8 Mon Sep 17 00:00:00 2001 From: Sebastian Silbermann Date: Mon, 5 Apr 2021 19:18:21 +0200 Subject: [PATCH] minor improvements to "adding non-standard attributes" --- docs/advanced/types-react-ap.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/advanced/types-react-ap.md b/docs/advanced/types-react-ap.md index 6ac5dd29..30a98d6d 100644 --- a/docs/advanced/types-react-ap.md +++ b/docs/advanced/types-react-ap.md @@ -130,9 +130,9 @@ Anything not listed above is considered an internal type and not public. If you' ### Adding non-standard attributes The attributes allowed on host components such as `button` or `img` follow the -HTML living standard. New features that are not yet part of specification +[HTML living standard](https://html.spec.whatwg.org/). New features that are not yet part of the living standard or are only implemented by certain browsers will therefore cause a type error. If -you specifically write code for these browsers or polyfill this attributes you can +you specifically write code for these browsers or polyfill these attributes you can use [module augmentation](https://www.typescriptlang.org/docs/handbook/declaration-merging.html#module-augmentation) to still get those components type checked without having to use `any` or `@ts-ignore`.