Skip to content

Question: Deliberately using 2 portal targets with same name #397

Open
@dsl101

Description

I couldn't see anything specific on this, but I have a use case where I'd like the same portal content be displayed in 2 different places. I've created 2 <portal-target name="xyz"> components, and of course currently getting the Target xyz already exists warning. I was about to disable that using the option, but wanted to check that this use is valid, or is it likely to cause other issues?

For what it's worth, it seems to be working fine...

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions