docs: Add Safari ITP documentation for setActive() decorateUrl

[nikosdouvlis]

🔎 Preview:

• https://clerk.com/docs/pr/nikos-safari-itp-docs/reference/javascript/clerk#using-the-navigate-parameter
• https://clerk.com/docs/pr/nikos-safari-itp-docs/reference/javascript/types/set-active-params

What changed?

Adds documentation for the Safari ITP cookie workaround introduced in clerk/javascript#7623

Summary

• Added decorateUrl parameter to SetActiveParams navigate callback documentation
• Added "Safari cookie limitations" section to the Clerk class reference explaining:
  • Why Safari's ITP limits cookies to 7 days
  • How to use decorateUrl to enable automatic cookie refresh
  • Code example showing the recommended pattern

Related

Add decorateUrl to navigate callbacks for Safari ITP support PR updates all code examples to use this new feature

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
clerk-docs	Ready	Preview	Feb 5, 2026 0:55am

[SarahSoutoul]

This looks good to me but just left one comment around the CLAUDE.md file, feeling out of place? Will approve once that's responded.

Also, @nikosdouvlis this change is meant to go into main right? Cause there is the other PR that's related to this but the base branch is core-3?

[SarahSoutoul]

@alexisintech if I can have a second pair of eyes on this?

[alexisintech]

@SarahSoutoul pushed a minor docs review. once @nikosdouvlis confirms if its for core 2 or for core 3, the relevant code examples across the docs need to be updated. so this PR is going to need another update.

e.g. if its for core 2, there are many custom flows that use the navigate() parameter and will need to use this decorateUrl() function.

[alexisintech]

@SarahSoutoul pushed a minor docs review. once @nikosdouvlis confirms if its for core 2 or for core 3, the relevant code examples across the docs need to be updated. so this PR is going to need another update.

e.g. if its for core 2, there are many custom flows that use the navigate() parameter and will need to use this decorateUrl() function.

actually, i've just seen this PR: Add decorateUrl to navigate callbacks for Safari ITP support
which is doing just that, and its for the core-3 branch. i think this PR is meant to go to the core-3 branch 😅 which would make sense because the clerk/javascript PR was merged to their main, which is core 3

[nikosdouvlis]

@SarahSoutoul pushed a minor docs review. once @nikosdouvlis confirms if its for core 2 or for core 3, the relevant code examples across the docs need to be updated. so this PR is going to need another update.
e.g. if its for core 2, there are many custom flows that use the navigate() parameter and will need to use this decorateUrl() function.

actually, i've just seen this PR: Add decorateUrl to navigate callbacks for Safari ITP support which is doing just that, and its for the core-3 branch. i think this PR is meant to go to the core-3 branch 😅 which would make sense because the clerk/javascript PR was merged to their main, which is core 3

Alexis is correct! I've updated the base branch, the mismatch between the repos got me once again. Apologies for the confusion

[SarahSoutoul]

@SarahSoutoul pushed a minor docs review. once @nikosdouvlis confirms if its for core 2 or for core 3, the relevant code examples across the docs need to be updated. so this PR is going to need another update.
e.g. if its for core 2, there are many custom flows that use the navigate() parameter and will need to use this decorateUrl() function.

actually, i've just seen this PR: Add decorateUrl to navigate callbacks for Safari ITP support which is doing just that, and its for the core-3 branch. i think this PR is meant to go to the core-3 branch 😅 which would make sense because the clerk/javascript PR was merged to their main, which is core 3

Yup, that's why I had this question here:

Also, @nikosdouvlis this change is meant to go into main right? Cause there is the other https://github.com/clerk/clerk-docs/pull/3037 that's related to this but the base branch is core-3?

Glad we've got it all figured out.

[nikosdouvlis]

🔎 Preview:

• https://clerk.com/docs/pr/nikos-safari-itp-docs/reference/javascript/clerk#using-the-navigate-parameter
• https://clerk.com/docs/pr/nikos-safari-itp-docs/reference/javascript/types/set-active-params

What changed?

Adds documentation for the Safari ITP cookie workaround introduced in clerk/javascript#7623

Summary

• Added decorateUrl parameter to SetActiveParams navigate callback documentation
• Added "Safari cookie limitations" section to the Clerk class reference explaining:
  • Why Safari's ITP limits cookies to 7 days
  • How to use decorateUrl to enable automatic cookie refresh
  • Code example showing the recommended pattern

Related

Add decorateUrl to navigate callbacks for Safari ITP support PR updates all code examples to use this new feature

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
clerk-docs	Ready	Preview	Feb 5, 2026 0:55am

[SarahSoutoul]

This looks good to me but just left one comment around the CLAUDE.md file, feeling out of place? Will approve once that's responded.

Also, @nikosdouvlis this change is meant to go into main right? Cause there is the other PR that's related to this but the base branch is core-3?

[SarahSoutoul]

@alexisintech if I can have a second pair of eyes on this?

[alexisintech]

@SarahSoutoul pushed a minor docs review. once @nikosdouvlis confirms if its for core 2 or for core 3, the relevant code examples across the docs need to be updated. so this PR is going to need another update.

e.g. if its for core 2, there are many custom flows that use the navigate() parameter and will need to use this decorateUrl() function.

[alexisintech]

@SarahSoutoul pushed a minor docs review. once @nikosdouvlis confirms if its for core 2 or for core 3, the relevant code examples across the docs need to be updated. so this PR is going to need another update.

e.g. if its for core 2, there are many custom flows that use the navigate() parameter and will need to use this decorateUrl() function.

actually, i've just seen this PR: Add decorateUrl to navigate callbacks for Safari ITP support
which is doing just that, and its for the core-3 branch. i think this PR is meant to go to the core-3 branch 😅 which would make sense because the clerk/javascript PR was merged to their main, which is core 3

[nikosdouvlis]

@SarahSoutoul pushed a minor docs review. once @nikosdouvlis confirms if its for core 2 or for core 3, the relevant code examples across the docs need to be updated. so this PR is going to need another update.
e.g. if its for core 2, there are many custom flows that use the navigate() parameter and will need to use this decorateUrl() function.

actually, i've just seen this PR: Add decorateUrl to navigate callbacks for Safari ITP support which is doing just that, and its for the core-3 branch. i think this PR is meant to go to the core-3 branch 😅 which would make sense because the clerk/javascript PR was merged to their main, which is core 3

Alexis is correct! I've updated the base branch, the mismatch between the repos got me once again. Apologies for the confusion

[SarahSoutoul]

@SarahSoutoul pushed a minor docs review. once @nikosdouvlis confirms if its for core 2 or for core 3, the relevant code examples across the docs need to be updated. so this PR is going to need another update.
e.g. if its for core 2, there are many custom flows that use the navigate() parameter and will need to use this decorateUrl() function.

actually, i've just seen this PR: Add decorateUrl to navigate callbacks for Safari ITP support which is doing just that, and its for the core-3 branch. i think this PR is meant to go to the core-3 branch 😅 which would make sense because the clerk/javascript PR was merged to their main, which is core 3

Yup, that's why I had this question here:

Also, @nikosdouvlis this change is meant to go into main right? Cause there is the other https://github.com/clerk/clerk-docs/pull/3037 that's related to this but the base branch is core-3?

Glad we've got it all figured out.

[nikosdouvlis]

🔎 Preview:

• https://clerk.com/docs/pr/nikos-safari-itp-docs/reference/javascript/clerk#using-the-navigate-parameter
• https://clerk.com/docs/pr/nikos-safari-itp-docs/reference/javascript/types/set-active-params

What changed?

Adds documentation for the Safari ITP cookie workaround introduced in clerk/javascript#7623

Summary

• Added decorateUrl parameter to SetActiveParams navigate callback documentation
• Added "Safari cookie limitations" section to the Clerk class reference explaining:
  • Why Safari's ITP limits cookies to 7 days
  • How to use decorateUrl to enable automatic cookie refresh
  • Code example showing the recommended pattern

Related

Add decorateUrl to navigate callbacks for Safari ITP support PR updates all code examples to use this new feature

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
clerk-docs	Ready	Preview	Feb 5, 2026 0:55am

[SarahSoutoul]

This looks good to me but just left one comment around the CLAUDE.md file, feeling out of place? Will approve once that's responded.

Also, @nikosdouvlis this change is meant to go into main right? Cause there is the other PR that's related to this but the base branch is core-3?

[SarahSoutoul]

@alexisintech if I can have a second pair of eyes on this?

[alexisintech]

@SarahSoutoul pushed a minor docs review. once @nikosdouvlis confirms if its for core 2 or for core 3, the relevant code examples across the docs need to be updated. so this PR is going to need another update.

e.g. if its for core 2, there are many custom flows that use the navigate() parameter and will need to use this decorateUrl() function.

[alexisintech]

@SarahSoutoul pushed a minor docs review. once @nikosdouvlis confirms if its for core 2 or for core 3, the relevant code examples across the docs need to be updated. so this PR is going to need another update.

e.g. if its for core 2, there are many custom flows that use the navigate() parameter and will need to use this decorateUrl() function.

actually, i've just seen this PR: Add decorateUrl to navigate callbacks for Safari ITP support
which is doing just that, and its for the core-3 branch. i think this PR is meant to go to the core-3 branch 😅 which would make sense because the clerk/javascript PR was merged to their main, which is core 3

[nikosdouvlis]

@SarahSoutoul pushed a minor docs review. once @nikosdouvlis confirms if its for core 2 or for core 3, the relevant code examples across the docs need to be updated. so this PR is going to need another update.
e.g. if its for core 2, there are many custom flows that use the navigate() parameter and will need to use this decorateUrl() function.

actually, i've just seen this PR: Add decorateUrl to navigate callbacks for Safari ITP support which is doing just that, and its for the core-3 branch. i think this PR is meant to go to the core-3 branch 😅 which would make sense because the clerk/javascript PR was merged to their main, which is core 3

Alexis is correct! I've updated the base branch, the mismatch between the repos got me once again. Apologies for the confusion

[SarahSoutoul]

@SarahSoutoul pushed a minor docs review. once @nikosdouvlis confirms if its for core 2 or for core 3, the relevant code examples across the docs need to be updated. so this PR is going to need another update.
e.g. if its for core 2, there are many custom flows that use the navigate() parameter and will need to use this decorateUrl() function.

actually, i've just seen this PR: Add decorateUrl to navigate callbacks for Safari ITP support which is doing just that, and its for the core-3 branch. i think this PR is meant to go to the core-3 branch 😅 which would make sense because the clerk/javascript PR was merged to their main, which is core 3

Yup, that's why I had this question here:

Also, @nikosdouvlis this change is meant to go into main right? Cause there is the other https://github.com/clerk/clerk-docs/pull/3037 that's related to this but the base branch is core-3?

Glad we've got it all figured out.

[nikosdouvlis]

🔎 Preview:

• https://clerk.com/docs/pr/nikos-safari-itp-docs/reference/javascript/clerk#using-the-navigate-parameter
• https://clerk.com/docs/pr/nikos-safari-itp-docs/reference/javascript/types/set-active-params

What changed?

Adds documentation for the Safari ITP cookie workaround introduced in clerk/javascript#7623

Summary

• Added decorateUrl parameter to SetActiveParams navigate callback documentation
• Added "Safari cookie limitations" section to the Clerk class reference explaining:
  • Why Safari's ITP limits cookies to 7 days
  • How to use decorateUrl to enable automatic cookie refresh
  • Code example showing the recommended pattern

Related

Add decorateUrl to navigate callbacks for Safari ITP support PR updates all code examples to use this new feature

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
clerk-docs	Ready	Preview	Feb 5, 2026 0:55am

[SarahSoutoul]

This looks good to me but just left one comment around the CLAUDE.md file, feeling out of place? Will approve once that's responded.

Also, @nikosdouvlis this change is meant to go into main right? Cause there is the other PR that's related to this but the base branch is core-3?

[SarahSoutoul]

@alexisintech if I can have a second pair of eyes on this?

[alexisintech]

@SarahSoutoul pushed a minor docs review. once @nikosdouvlis confirms if its for core 2 or for core 3, the relevant code examples across the docs need to be updated. so this PR is going to need another update.

e.g. if its for core 2, there are many custom flows that use the navigate() parameter and will need to use this decorateUrl() function.

[alexisintech]

@SarahSoutoul pushed a minor docs review. once @nikosdouvlis confirms if its for core 2 or for core 3, the relevant code examples across the docs need to be updated. so this PR is going to need another update.

e.g. if its for core 2, there are many custom flows that use the navigate() parameter and will need to use this decorateUrl() function.

actually, i've just seen this PR: Add decorateUrl to navigate callbacks for Safari ITP support
which is doing just that, and its for the core-3 branch. i think this PR is meant to go to the core-3 branch 😅 which would make sense because the clerk/javascript PR was merged to their main, which is core 3

[nikosdouvlis]

@SarahSoutoul pushed a minor docs review. once @nikosdouvlis confirms if its for core 2 or for core 3, the relevant code examples across the docs need to be updated. so this PR is going to need another update.
e.g. if its for core 2, there are many custom flows that use the navigate() parameter and will need to use this decorateUrl() function.

actually, i've just seen this PR: Add decorateUrl to navigate callbacks for Safari ITP support which is doing just that, and its for the core-3 branch. i think this PR is meant to go to the core-3 branch 😅 which would make sense because the clerk/javascript PR was merged to their main, which is core 3

Alexis is correct! I've updated the base branch, the mismatch between the repos got me once again. Apologies for the confusion

[SarahSoutoul]

@SarahSoutoul pushed a minor docs review. once @nikosdouvlis confirms if its for core 2 or for core 3, the relevant code examples across the docs need to be updated. so this PR is going to need another update.
e.g. if its for core 2, there are many custom flows that use the navigate() parameter and will need to use this decorateUrl() function.

actually, i've just seen this PR: Add decorateUrl to navigate callbacks for Safari ITP support which is doing just that, and its for the core-3 branch. i think this PR is meant to go to the core-3 branch 😅 which would make sense because the clerk/javascript PR was merged to their main, which is core 3

Yup, that's why I had this question here:

Also, @nikosdouvlis this change is meant to go into main right? Cause there is the other https://github.com/clerk/clerk-docs/pull/3037 that's related to this but the base branch is core-3?

Glad we've got it all figured out.

[nikosdouvlis]

🔎 Preview:

• https://clerk.com/docs/pr/nikos-safari-itp-docs/reference/javascript/clerk#using-the-navigate-parameter
• https://clerk.com/docs/pr/nikos-safari-itp-docs/reference/javascript/types/set-active-params

What changed?

Adds documentation for the Safari ITP cookie workaround introduced in clerk/javascript#7623

Summary

• Added decorateUrl parameter to SetActiveParams navigate callback documentation
• Added "Safari cookie limitations" section to the Clerk class reference explaining:
  • Why Safari's ITP limits cookies to 7 days
  • How to use decorateUrl to enable automatic cookie refresh
  • Code example showing the recommended pattern

Related

Add decorateUrl to navigate callbacks for Safari ITP support PR updates all code examples to use this new feature

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
clerk-docs	Ready	Preview	Feb 5, 2026 0:55am

[SarahSoutoul]

This looks good to me but just left one comment around the CLAUDE.md file, feeling out of place? Will approve once that's responded.

Also, @nikosdouvlis this change is meant to go into main right? Cause there is the other PR that's related to this but the base branch is core-3?

[SarahSoutoul]

@alexisintech if I can have a second pair of eyes on this?

[alexisintech]

@SarahSoutoul pushed a minor docs review. once @nikosdouvlis confirms if its for core 2 or for core 3, the relevant code examples across the docs need to be updated. so this PR is going to need another update.

e.g. if its for core 2, there are many custom flows that use the navigate() parameter and will need to use this decorateUrl() function.

[alexisintech]

@SarahSoutoul pushed a minor docs review. once @nikosdouvlis confirms if its for core 2 or for core 3, the relevant code examples across the docs need to be updated. so this PR is going to need another update.

e.g. if its for core 2, there are many custom flows that use the navigate() parameter and will need to use this decorateUrl() function.

actually, i've just seen this PR: Add decorateUrl to navigate callbacks for Safari ITP support
which is doing just that, and its for the core-3 branch. i think this PR is meant to go to the core-3 branch 😅 which would make sense because the clerk/javascript PR was merged to their main, which is core 3

[nikosdouvlis]

@SarahSoutoul pushed a minor docs review. once @nikosdouvlis confirms if its for core 2 or for core 3, the relevant code examples across the docs need to be updated. so this PR is going to need another update.
e.g. if its for core 2, there are many custom flows that use the navigate() parameter and will need to use this decorateUrl() function.

actually, i've just seen this PR: Add decorateUrl to navigate callbacks for Safari ITP support which is doing just that, and its for the core-3 branch. i think this PR is meant to go to the core-3 branch 😅 which would make sense because the clerk/javascript PR was merged to their main, which is core 3

Alexis is correct! I've updated the base branch, the mismatch between the repos got me once again. Apologies for the confusion

[SarahSoutoul]

@SarahSoutoul pushed a minor docs review. once @nikosdouvlis confirms if its for core 2 or for core 3, the relevant code examples across the docs need to be updated. so this PR is going to need another update.
e.g. if its for core 2, there are many custom flows that use the navigate() parameter and will need to use this decorateUrl() function.

actually, i've just seen this PR: Add decorateUrl to navigate callbacks for Safari ITP support which is doing just that, and its for the core-3 branch. i think this PR is meant to go to the core-3 branch 😅 which would make sense because the clerk/javascript PR was merged to their main, which is core 3

Yup, that's why I had this question here:

Also, @nikosdouvlis this change is meant to go into main right? Cause there is the other https://github.com/clerk/clerk-docs/pull/3037 that's related to this but the base branch is core-3?

Glad we've got it all figured out.

[nikosdouvlis]

🔎 Preview:

• https://clerk.com/docs/pr/nikos-safari-itp-docs/reference/javascript/clerk#using-the-navigate-parameter
• https://clerk.com/docs/pr/nikos-safari-itp-docs/reference/javascript/types/set-active-params

What changed?

Adds documentation for the Safari ITP cookie workaround introduced in clerk/javascript#7623

Summary

• Added decorateUrl parameter to SetActiveParams navigate callback documentation
• Added "Safari cookie limitations" section to the Clerk class reference explaining:
  • Why Safari's ITP limits cookies to 7 days
  • How to use decorateUrl to enable automatic cookie refresh
  • Code example showing the recommended pattern

Related

Add decorateUrl to navigate callbacks for Safari ITP support PR updates all code examples to use this new feature

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
clerk-docs	Ready	Preview	Feb 5, 2026 0:55am

[SarahSoutoul]

This looks good to me but just left one comment around the CLAUDE.md file, feeling out of place? Will approve once that's responded.

Also, @nikosdouvlis this change is meant to go into main right? Cause there is the other PR that's related to this but the base branch is core-3?

[SarahSoutoul]

@alexisintech if I can have a second pair of eyes on this?

[alexisintech]

@SarahSoutoul pushed a minor docs review. once @nikosdouvlis confirms if its for core 2 or for core 3, the relevant code examples across the docs need to be updated. so this PR is going to need another update.

e.g. if its for core 2, there are many custom flows that use the navigate() parameter and will need to use this decorateUrl() function.

[alexisintech]

@SarahSoutoul pushed a minor docs review. once @nikosdouvlis confirms if its for core 2 or for core 3, the relevant code examples across the docs need to be updated. so this PR is going to need another update.

e.g. if its for core 2, there are many custom flows that use the navigate() parameter and will need to use this decorateUrl() function.

actually, i've just seen this PR: Add decorateUrl to navigate callbacks for Safari ITP support
which is doing just that, and its for the core-3 branch. i think this PR is meant to go to the core-3 branch 😅 which would make sense because the clerk/javascript PR was merged to their main, which is core 3

[nikosdouvlis]

@SarahSoutoul pushed a minor docs review. once @nikosdouvlis confirms if its for core 2 or for core 3, the relevant code examples across the docs need to be updated. so this PR is going to need another update.
e.g. if its for core 2, there are many custom flows that use the navigate() parameter and will need to use this decorateUrl() function.

actually, i've just seen this PR: Add decorateUrl to navigate callbacks for Safari ITP support which is doing just that, and its for the core-3 branch. i think this PR is meant to go to the core-3 branch 😅 which would make sense because the clerk/javascript PR was merged to their main, which is core 3

Alexis is correct! I've updated the base branch, the mismatch between the repos got me once again. Apologies for the confusion

[SarahSoutoul]

@SarahSoutoul pushed a minor docs review. once @nikosdouvlis confirms if its for core 2 or for core 3, the relevant code examples across the docs need to be updated. so this PR is going to need another update.
e.g. if its for core 2, there are many custom flows that use the navigate() parameter and will need to use this decorateUrl() function.

actually, i've just seen this PR: Add decorateUrl to navigate callbacks for Safari ITP support which is doing just that, and its for the core-3 branch. i think this PR is meant to go to the core-3 branch 😅 which would make sense because the clerk/javascript PR was merged to their main, which is core 3

Yup, that's why I had this question here:

Also, @nikosdouvlis this change is meant to go into main right? Cause there is the other https://github.com/clerk/clerk-docs/pull/3037 that's related to this but the base branch is core-3?

Glad we've got it all figured out.

[nikosdouvlis]

🔎 Preview:

• https://clerk.com/docs/pr/nikos-safari-itp-docs/reference/javascript/clerk#using-the-navigate-parameter
• https://clerk.com/docs/pr/nikos-safari-itp-docs/reference/javascript/types/set-active-params

What changed?

Adds documentation for the Safari ITP cookie workaround introduced in clerk/javascript#7623

Summary

• Added decorateUrl parameter to SetActiveParams navigate callback documentation
• Added "Safari cookie limitations" section to the Clerk class reference explaining:
  • Why Safari's ITP limits cookies to 7 days
  • How to use decorateUrl to enable automatic cookie refresh
  • Code example showing the recommended pattern

Related

Add decorateUrl to navigate callbacks for Safari ITP support PR updates all code examples to use this new feature

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
clerk-docs	Ready	Preview	Feb 5, 2026 0:55am

[SarahSoutoul]

This looks good to me but just left one comment around the CLAUDE.md file, feeling out of place? Will approve once that's responded.

Also, @nikosdouvlis this change is meant to go into main right? Cause there is the other PR that's related to this but the base branch is core-3?

[SarahSoutoul]

@alexisintech if I can have a second pair of eyes on this?

[alexisintech]

@SarahSoutoul pushed a minor docs review. once @nikosdouvlis confirms if its for core 2 or for core 3, the relevant code examples across the docs need to be updated. so this PR is going to need another update.

e.g. if its for core 2, there are many custom flows that use the navigate() parameter and will need to use this decorateUrl() function.

[alexisintech]

@SarahSoutoul pushed a minor docs review. once @nikosdouvlis confirms if its for core 2 or for core 3, the relevant code examples across the docs need to be updated. so this PR is going to need another update.

e.g. if its for core 2, there are many custom flows that use the navigate() parameter and will need to use this decorateUrl() function.

actually, i've just seen this PR: Add decorateUrl to navigate callbacks for Safari ITP support
which is doing just that, and its for the core-3 branch. i think this PR is meant to go to the core-3 branch 😅 which would make sense because the clerk/javascript PR was merged to their main, which is core 3

[nikosdouvlis]

@SarahSoutoul pushed a minor docs review. once @nikosdouvlis confirms if its for core 2 or for core 3, the relevant code examples across the docs need to be updated. so this PR is going to need another update.
e.g. if its for core 2, there are many custom flows that use the navigate() parameter and will need to use this decorateUrl() function.

actually, i've just seen this PR: Add decorateUrl to navigate callbacks for Safari ITP support which is doing just that, and its for the core-3 branch. i think this PR is meant to go to the core-3 branch 😅 which would make sense because the clerk/javascript PR was merged to their main, which is core 3

Alexis is correct! I've updated the base branch, the mismatch between the repos got me once again. Apologies for the confusion

[SarahSoutoul]

@SarahSoutoul pushed a minor docs review. once @nikosdouvlis confirms if its for core 2 or for core 3, the relevant code examples across the docs need to be updated. so this PR is going to need another update.
e.g. if its for core 2, there are many custom flows that use the navigate() parameter and will need to use this decorateUrl() function.

actually, i've just seen this PR: Add decorateUrl to navigate callbacks for Safari ITP support which is doing just that, and its for the core-3 branch. i think this PR is meant to go to the core-3 branch 😅 which would make sense because the clerk/javascript PR was merged to their main, which is core 3

Yup, that's why I had this question here:

Also, @nikosdouvlis this change is meant to go into main right? Cause there is the other https://github.com/clerk/clerk-docs/pull/3037 that's related to this but the base branch is core-3?

Glad we've got it all figured out.

[nikosdouvlis]

🔎 Preview:

• https://clerk.com/docs/pr/nikos-safari-itp-docs/reference/javascript/clerk#using-the-navigate-parameter
• https://clerk.com/docs/pr/nikos-safari-itp-docs/reference/javascript/types/set-active-params

What changed?

Adds documentation for the Safari ITP cookie workaround introduced in clerk/javascript#7623

Summary

• Added decorateUrl parameter to SetActiveParams navigate callback documentation
• Added "Safari cookie limitations" section to the Clerk class reference explaining:
  • Why Safari's ITP limits cookies to 7 days
  • How to use decorateUrl to enable automatic cookie refresh
  • Code example showing the recommended pattern

Related

Add decorateUrl to navigate callbacks for Safari ITP support PR updates all code examples to use this new feature

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
clerk-docs	Ready	Preview	Feb 5, 2026 0:55am

[SarahSoutoul]

This looks good to me but just left one comment around the CLAUDE.md file, feeling out of place? Will approve once that's responded.

Also, @nikosdouvlis this change is meant to go into main right? Cause there is the other PR that's related to this but the base branch is core-3?

[SarahSoutoul]

@alexisintech if I can have a second pair of eyes on this?

[alexisintech]

@SarahSoutoul pushed a minor docs review. once @nikosdouvlis confirms if its for core 2 or for core 3, the relevant code examples across the docs need to be updated. so this PR is going to need another update.

e.g. if its for core 2, there are many custom flows that use the navigate() parameter and will need to use this decorateUrl() function.

[alexisintech]

@SarahSoutoul pushed a minor docs review. once @nikosdouvlis confirms if its for core 2 or for core 3, the relevant code examples across the docs need to be updated. so this PR is going to need another update.

e.g. if its for core 2, there are many custom flows that use the navigate() parameter and will need to use this decorateUrl() function.

actually, i've just seen this PR: Add decorateUrl to navigate callbacks for Safari ITP support
which is doing just that, and its for the core-3 branch. i think this PR is meant to go to the core-3 branch 😅 which would make sense because the clerk/javascript PR was merged to their main, which is core 3

[nikosdouvlis]

@SarahSoutoul pushed a minor docs review. once @nikosdouvlis confirms if its for core 2 or for core 3, the relevant code examples across the docs need to be updated. so this PR is going to need another update.
e.g. if its for core 2, there are many custom flows that use the navigate() parameter and will need to use this decorateUrl() function.

actually, i've just seen this PR: Add decorateUrl to navigate callbacks for Safari ITP support which is doing just that, and its for the core-3 branch. i think this PR is meant to go to the core-3 branch 😅 which would make sense because the clerk/javascript PR was merged to their main, which is core 3

Alexis is correct! I've updated the base branch, the mismatch between the repos got me once again. Apologies for the confusion

[SarahSoutoul]

@SarahSoutoul pushed a minor docs review. once @nikosdouvlis confirms if its for core 2 or for core 3, the relevant code examples across the docs need to be updated. so this PR is going to need another update.
e.g. if its for core 2, there are many custom flows that use the navigate() parameter and will need to use this decorateUrl() function.

actually, i've just seen this PR: Add decorateUrl to navigate callbacks for Safari ITP support which is doing just that, and its for the core-3 branch. i think this PR is meant to go to the core-3 branch 😅 which would make sense because the clerk/javascript PR was merged to their main, which is core 3

Yup, that's why I had this question here:

Also, @nikosdouvlis this change is meant to go into main right? Cause there is the other https://github.com/clerk/clerk-docs/pull/3037 that's related to this but the base branch is core-3?

Glad we've got it all figured out.