<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugs.webkit.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.4.1"
          urlbase="https://bugs.webkit.org/"
          
          maintainer="admin@webkit.org"
>

    <bug>
          <bug_id>292975</bug_id>
          
          <creation_ts>2025-05-14 00:29:09 -0700</creation_ts>
          <short_desc>Partitioned cookies not working in Safari 18.5</short_desc>
          <delta_ts>2026-01-12 01:32:47 -0800</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>WebKit</product>
          <component>New Bugs</component>
          <version>WebKit Nightly Build</version>
          <rep_platform>Unspecified</rep_platform>
          <op_sys>Unspecified</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>CONFIGURATION CHANGED</resolution>
          
          <see_also>https://bugs.webkit.org/show_bug.cgi?id=293618</see_also>
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords>InRadar</keywords>
          <priority>P2</priority>
          <bug_severity>Normal</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Yoav Weiss">yoav</reporter>
          <assigned_to name="Nobody">webkit-unassigned</assigned_to>
          <cc>amodpandey</cc>
    
    <cc>annevk</cc>
    
    <cc>dara.hak</cc>
    
    <cc>helhum</cc>
    
    <cc>hermans.je</cc>
    
    <cc>isoengas</cc>
    
    <cc>jsminted+bugzilla</cc>
    
    <cc>katyayani.reddy</cc>
    
    <cc>kenner1</cc>
    
    <cc>lcswillems</cc>
    
    <cc>m_finkel</cc>
    
    <cc>natewiebe13</cc>
    
    <cc>ntim</cc>
    
    <cc>osku.tervonen</cc>
    
    <cc>ozan</cc>
    
    <cc>ramzabdae</cc>
    
    <cc>rshan181818</cc>
    
    <cc>sarjupatel</cc>
    
    <cc>tome</cc>
    
    <cc>tom</cc>
    
    <cc>webkit-bug-importer</cc>
    
    <cc>webkit.org</cc>
    
    <cc>wilander</cc>
          

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>2116976</commentid>
    <comment_count>0</comment_count>
    <who name="Yoav Weiss">yoav</who>
    <bug_when>2025-05-14 00:29:09 -0700</bug_when>
    <thetext>Reproduction test case: https://chips-site-a.glitch.me

Partitioned cookies worked in 18.4 and stopped working somewhere between that and 18.5

Trying to (manually) bisect, I see they already weren&apos;t working in 286403, the last commit of STP 208. (Earlier archived builds are unrelatedly crashing on my machine)</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>2117025</commentid>
    <comment_count>1</comment_count>
    <who name="John Wilander">wilander</who>
    <bug_when>2025-05-14 06:59:44 -0700</bug_when>
    <thetext>Hi, Yoav, and thanks for filing!

We unfortunately had to turn CHIPS off due to a serious bug that was too complex to address in the software update. The bug is not in WebKit. We don’t know right now when we’ll be able to turn it back on. Sorry about that.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>2117126</commentid>
    <comment_count>2</comment_count>
    <who name="Yoav Weiss">yoav</who>
    <bug_when>2025-05-14 12:24:04 -0700</bug_when>
    <thetext>Thanks for the update!</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>2117618</commentid>
    <comment_count>3</comment_count>
    <who name="Anchor Ed">jsminted+bugzilla</who>
    <bug_when>2025-05-16 08:24:51 -0700</bug_when>
    <thetext>Hey! Was about to report this same or similar issue.

It seems that with partitioned cookies turned off, cookies that are partitioned are getting entirely rejected (instead of being set without partitioning as was the previous experience).

Interestingly, they seem to get still get set when the dev tools are open making this very tricky to debug.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>2118604</commentid>
    <comment_count>4</comment_count>
    <who name="Radar WebKit Bug Importer">webkit-bug-importer</who>
    <bug_when>2025-05-21 00:30:14 -0700</bug_when>
    <thetext>&lt;rdar://problem/151755274&gt;</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>2119075</commentid>
    <comment_count>5</comment_count>
    <who name="Constructory">ozan</who>
    <bug_when>2025-05-22 14:01:36 -0700</bug_when>
    <thetext>How is this labeled as a &apos;normal&apos; severity bug? Is this how things usually done now ? This has potential to collapse most of the integrations done on some major industries. Are we just going to say that some guy at developing webkit handicapped cookies so bear with us ? This place needs a Linus Torvalds....</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>2119081</commentid>
    <comment_count>6</comment_count>
    <who name="John Wilander">wilander</who>
    <bug_when>2025-05-22 14:21:51 -0700</bug_when>
    <thetext>CHIPS was enabled in our .4 releases and disabled in .5 due to a serious bug. Partitioned cookies with CHIPS are opt-in.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>2119083</commentid>
    <comment_count>7</comment_count>
    <who name="Anchor Ed">jsminted+bugzilla</who>
    <bug_when>2025-05-22 14:26:04 -0700</bug_when>
    <thetext>Unfortunately disabling CHIPS in .5 blocks any partitioned cookie from being set now. Previous to .4 they would still be set, but as if they were not partitioned.

Our workaround at the moment is to detect safari and explicitly not set partitioned cookies.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>2119084</commentid>
    <comment_count>8</comment_count>
    <who name="Anchor Ed">jsminted+bugzilla</who>
    <bug_when>2025-05-22 14:27:50 -0700</bug_when>
    <thetext>I do really appreciate CHIPS being brought to Safari, though! Hope it gets re-enabled soon!</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>2119101</commentid>
    <comment_count>9</comment_count>
    <who name="Constructory">ozan</who>
    <bug_when>2025-05-22 15:05:23 -0700</bug_when>
    <thetext>3rd party iframes that previously functioned correctly using partitioned cookies are now failing entirely. Users are unable to log in to embedded content. This is not a minor issue. These integrations were stable and compliant in Safari .4, and if memory serves, the adoption of partitioned cookies followed Safari’s own guidance at the time.

With the release of .5 and CHIPS being disabled (and kneecapping partitioned cookies all together), we’re now forced to re-architect authentication flows under pressure. This introduces sudden instability to systems used by millions.

The lack of partitioned cookie support in Safari .5 has widespread consequences that go far beyond a typical regression.

I kindly urge webkit team to treat this issue with appropriate severity. Any assistance from staff cc&apos;d on this thread in helping escalate or clarify the timeline would be greatly appreciated.


-----------------------
&gt;To: Anchor Ed
Thank you for the workaround. Relayed it to the teams, seems like we will follow a similar path.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>2119117</commentid>
    <comment_count>10</comment_count>
    <who name="Matthew Finkel">m_finkel</who>
    <bug_when>2025-05-22 15:58:59 -0700</bug_when>
    <thetext>Safari 18.4 was released on March 31: https://webkit.org/blog/16574/webkit-features-in-safari-18-4/. In earlier versions of Safari, any cross-site cookies were not accepted in cross-site iframes (even if they were &quot;Partitioned&quot;), unless the iframe requested access to its &quot;first party&quot; cookies using the storage access API and the user granted access. Cookies that are set by the main web site should still be accepted, even if they include the &quot;Partitioned&quot; attribute.

Safari 18.5 should accept the same cookies as Safari 18.3. Are there web sites that worked in Safari 18.3 and 18.4, but they are now broken in 18.5?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>2119282</commentid>
    <comment_count>11</comment_count>
    <who name="Julian A">kenner1</who>
    <bug_when>2025-05-23 08:07:37 -0700</bug_when>
    <thetext>The issue stems from document.cookie and cookies set with the Partitioned flag, even in first-party contexts. If you visit https://chips-site-b.glitch.me/, you&apos;ll notice that it sets the following:

document.cookie = &quot;__Site-B-partitioned-cookie=123; Secure; Max-Age=84600; Path=/; SameSite=None; Partitioned;&quot;;

This is a first-party cookie, but the presence of the Partitioned flag prevents it from being stored. What&apos;s frustrating is that it sometimes works, making it difficult to debug. Version 18.4 and 18.5.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>2119328</commentid>
    <comment_count>12</comment_count>
    <who name="Anchor Ed">jsminted+bugzilla</who>
    <bug_when>2025-05-23 11:36:34 -0700</bug_when>
    <thetext>It seems to work when the dev tools have been opened at least once in the tab/session. Makes it very difficult to debug.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>2120060</commentid>
    <comment_count>13</comment_count>
    <who name="John Wilander">wilander</who>
    <bug_when>2025-05-27 21:23:03 -0700</bug_when>
    <thetext>*** Bug 293618 has been marked as a duplicate of this bug. ***</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>2127387</commentid>
    <comment_count>14</comment_count>
    <who name="Yoav Weiss">yoav</who>
    <bug_when>2025-07-02 13:49:11 -0700</bug_when>
    <thetext>Hey John and Matthew! Any updates you can share on this?
Any information you may be able to share regarding the timelines here can be very helpful :)</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>2127423</commentid>
    <comment_count>15</comment_count>
    <who name="John Wilander">wilander</who>
    <bug_when>2025-07-02 15:11:49 -0700</bug_when>
    <thetext>Nothing at this point. Re-enabling CHIPS is in part dependent on changes in underlying frameworks which means following along in open source will not tell you the whole story. Safari Technology Preview might not tell you the whole story either since it doesn&apos;t change underlying frameworks.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>2127532</commentid>
    <comment_count>16</comment_count>
    <who name="Yoav Weiss">yoav</who>
    <bug_when>2025-07-03 00:04:43 -0700</bug_when>
    <thetext>OK, thanks for the update!!</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>2143652</commentid>
    <comment_count>17</comment_count>
    <who name="">katyayani.reddy</who>
    <bug_when>2025-09-17 09:55:10 -0700</bug_when>
    <thetext>Hi John, Matthew,
It would be helpful if you could provide an update on when this will be available.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>2146202</commentid>
    <comment_count>18</comment_count>
    <who name="Lucas Willems">lcswillems</who>
    <bug_when>2025-09-26 09:48:31 -0700</bug_when>
    <thetext>Hey John, could you tell us more about the issues in the underlying frameworks preventing CHIPS to be re-enabled? And would you have a rough ETA? (e.g. a few weeks, months, or years)

Thank you very much! Having CHIPS enabled in Safari would allow my iframes to work seamlessly in Safari, which would be a big improvement.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>2146206</commentid>
    <comment_count>19</comment_count>
    <who name="John Wilander">wilander</who>
    <bug_when>2025-09-26 09:54:05 -0700</bug_when>
    <thetext>(In reply to lcswillems from comment #18)
&gt; Hey John, could you tell us more about the issues in the underlying
&gt; frameworks preventing CHIPS to be re-enabled?
HTTP and lower networking is not part of the WebKit open source project, and cookies are part of HTTP. Apple is not able to share more details for networking frameworks since ours are not open source. Other ports of WebKit may be able to share.

&gt; And would you have a rough  ETA? (e.g. a few weeks, months, or years)
We don&apos;t share plans for the future beyond what&apos;s in our software seeding and Safari Technology Preview. Looking at release notes and testing software update seeds is the way to go.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>2157915</commentid>
    <comment_count>20</comment_count>
    <who name="">amodpandey</who>
    <bug_when>2025-11-11 06:25:47 -0800</bug_when>
    <thetext>https://developer.apple.com/documentation/safari-release-notes/safari-26_2-release-notes#Privacy</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>2158695</commentid>
    <comment_count>21</comment_count>
    <who name="Tim Nguyen (:ntim)">ntim</who>
    <bug_when>2025-11-13 18:30:16 -0800</bug_when>
    <thetext>CHIPS is now back in Safari 26.2 beta.</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>