- Issue created by @jessebaker
- @jessebaker opened merge request.
- πΊπΈUnited States bnjmnm Ann Arbor, MI
I'm running into some situations where the problem still exists:
Scenario 1
I tested with this as the slot-containing component
const Slotto = ({ title = "Has Slots", one, two, three }) => { return ( <> {/* Text Prop */} <h3>{title} </h3> {/* Slot */} {one} {/* Slot */} {two} {/* Slot */} {three} </> ); };
And the outline is only around the
<h3>
, not the entire component including the slotsScenario 2
Largely the same component as above, but change
<h3>{title} </h3>
to
{title}
In this use case, there is no outline or nametag at all
Scenario 3
Take the component from scenario 2 but replace the fragment with a div, and it works great
- π¬π§United Kingdom jessebaker
I've just seen there was a collision when I added the file when updating the IS. So adding the files again just in case.
-
jessebaker β
committed 9eebf987 on 0.x
Issue #3536328 by jessebaker, bnjmnm: Component/slot overlay borders can...
-
jessebaker β
committed 9eebf987 on 0.x
-
jessebaker β
committed 9eebf987 on 0.x-hotfix-cli-tests
Issue #3536328 by jessebaker, bnjmnm: Component/slot overlay borders can...
-
jessebaker β
committed 9eebf987 on 0.x-hotfix-cli-tests
- π¬π§United Kingdom jessebaker
I've created a follow up π Investigate the use of React fragments in JS components Active in response to the issue with React fragments mentioned in #4.