Skip to content

Documentation on duplicate tags in <Head> is unclear #2749

@zachauten

Description

@zachauten

The docs on avoiding duplicate tags while modifying the <head> state that:

To ensure that the tag is not duplicated, Fresh supports setting the key prop. By giving matching elements the same key prop, only the last one will be rendered.

But it does not explain what determines which one will be "last". Is this something that can be controlled? I'm running into an issue where I've defined some default values in the head in my _app.tsx, but I want to override them in the route component, but the ones in _app.tsx are taking precedence.

Am I missing something? Thanks in advance!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions