Skip to content

docs: Add Safari ITP documentation for setActive() decorateUrl#3013

Merged
nikosdouvlis merged 7 commits intocore-3from
nikos/safari-itp-docs
Feb 6, 2026
Merged

docs: Add Safari ITP documentation for setActive() decorateUrl#3013
nikosdouvlis merged 7 commits intocore-3from
nikos/safari-itp-docs

Conversation

@nikosdouvlis
Copy link
Member

@nikosdouvlis nikosdouvlis commented Jan 29, 2026

🔎 Preview:

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

@nikosdouvlis nikosdouvlis requested a review from a team as a code owner January 29, 2026 13:37
@vercel
Copy link

vercel bot commented Jan 29, 2026

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

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

Request Review

Add documentation for the Safari cookie limitation workaround:
- Added decorateUrl parameter to SetActiveParams navigate callback
- Added Safari cookie limitations section to Clerk class reference
- Fix Sarah's comments: navigation URLs → destination URLs, em-dash → spaced dash
- Address Bryce's comment: clarify that ITP affects __client cookie specifically,
  not all JS cookies. The limitation is due to CNAME cloaking on clerk. subdomain
@SarahSoutoul
Copy link
Contributor

SarahSoutoul commented Feb 4, 2026

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
Copy link
Contributor

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

@alexisintech
Copy link
Member

alexisintech commented Feb 5, 2026

@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
Copy link
Member

@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
Copy link
Member Author

@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
Copy link
Contributor

@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 nikosdouvlis merged commit e5a6830 into core-3 Feb 6, 2026
8 checks passed
@nikosdouvlis nikosdouvlis deleted the nikos/safari-itp-docs branch February 6, 2026 09:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants