docs(config): add documentation for scopedSlotTextContentFix#767
Conversation
|
This pull request is being automatically deployed with Vercel (learn more). stencil-site – ./🔍 Inspect: https://vercel.com/ionic/stencil-site/HZWxvaVtpvRrQJ2wNnpnaciMP5VW stencil-site-ionic-io – ./🔍 Inspect: https://vercel.com/ionic/stencil-site-ionic-io/7p5eUazjUBP7yh4TWXx4YkKEPA6G |
src/docs/config/extras.md
Outdated
|
|
||
| ### scopedSlotTextContentFix | ||
|
|
||
| An experimental flag that when set to `true`, aligns the behavior of invoking the `textContent` getter/setter on a scoped component to act more like a component that uses the shadow DOM. Defaults to `false`. |
There was a problem hiding this comment.
How does it behave that makes it more like a component that uses the shadow DOM? This may be unclear if the reader doesn't know what the behavior for a component using shadow DOM is.
There was a problem hiding this comment.
I updated the verbiage to point to the spec. That may not be the most user friendly thing TBH, but spelling out every single scenario would be pretty cumbersome. Alternatively, we could link https://developer.mozilla.org/en-US/docs/Web/API/Node/textContent#description, but I don't know if one should be considered "better" than the other - the MDN one is definitely more user friendly, but the spec is, well, the spec 😛 LMK what you think
There was a problem hiding this comment.
Yeah tough call, but I think I would lean more towards MDN. At the end of the day, the docs are meant to be informative and understandable/user friendly, so as long as MDN provides all the necessary info (and I believe it does) I would choose it for its user friendliness.
Add documentation for stenciljs/core#3047