I've recently been porting a Chrome extension to Safari, and encountered this kind of error (bug, feature, etc.)
So, in global page i have a XMLHTTP request to a secure page which is available only after you login.
Example:
it seems that global page somewhat has it's own cookies, so a secure page thinks i'm new
ps: in Chrome i can load that page and it thinks i'm acting on behalf of logged in user, so i guess there are some restrictions in Safari
pps: i heard there's a Block third-party cookies option in Safari, but even if i checked it to "Never block" it still doesn't work
SAFARI for iOS (iPhone and iPad)Step 1: Go to Settings, then scroll down and select “Safari”. Step 2: Scroll down to “Privacy & Security”. Step 3: Verify “Block All Cookies” is ticked (green/white), click to allow cookies. Step 4: Clear the browser cache and reopen the browser.
Click Safari > Preferences and click the “Privacy” tab. Make a note about what is currently selected. Under “Cookies and website data”, click “Always Allow”.
With the Cookies API your extensions have access to capabilities similar to those used by websites to store and read cookies.
Unfortunately the problem is still existent in safari 5.1.7 windows version.
I've found a workaround to pass login credentials (username/password pairs) to the global page using message passing and global page use them to login silently.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With