Timeline for Set cookie inside iFrame domain not seen
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 8 at 16:47 | comment | added | browsermator | Make sure they are both https. Current rules prohibit http for same-site: none. Some browsers I think have already changed the same-site: none rules so that you need to set "partitioned" explicitly: developer.mozilla.org/en-US/docs/Web/Privacy/Privacy_sandbox/… | |
| May 8 at 16:19 | comment | added | browsermator | partitioning would only keep these cookies in their a/b context. It doesn't prevent them being sent it just separates them into different cookie "jars" that include the parent context. If b's frame were in some other site's context, none of the cookies set from a/b context would be sent to newsite/b context. | |
| Mar 13, 2023 at 22:01 | comment | added | Los Sol | I've found that the behavior is due to dynamic state partitioning | |
| Mar 13, 2023 at 10:04 | comment | added | mentallurg | This has nothing to do with 3rd party cookies. When the windows a.com receives a messages, it sets cookie for its own domain, a.com. If settings for 3rd party cookies affect that, it means, you are doing something wrong. | |
| Mar 13, 2023 at 9:29 | comment | added | Los Sol | see my answer with firefox screenshots | |
| Mar 13, 2023 at 8:51 | history | answered | mentallurg | CC BY-SA 4.0 |