rgleeson@ do you have a reproduction URI or some type of example we can try?

Hi dtapu...@chromium.org,
Attached is an extension that reproduces the issue.
Here are the reproduction steps:
1) Load extension
2) Double check the extension can access file:/// URLs (for the next step).
2) Visit file:///<path to unzipped directory>/iframepage.html
3) Afterwards, inspect the background page's console. If it worked, you should see the URL in the iframe (https://www.aerlingius.ie). If it didn't work, you will see nothing. I see nothing.

The source might also be useful to you - i don't know the best way to provide a reproduction case for this.

Deleted: bug703128.zip 12.3 KB

bug703128.zip 12.3 KB Download

Thank you for providing more feedback. Adding requester "dtapuska@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Sorry, I had a mistake in the last zip. Corrected version is attached.

Deleted: bug703128.zip 12.4 KB

bug703128.zip 12.4 KB Download

Over to platform>extensions.

I believe this is the lifecycle of the request. The onHeadersReceived is called in the context of the new iframe and your extension likely hasn't been instantiated yet.

Sorry, I don't think my reproduction case was very good.
I see that onHeadersReceived is never called with the real extension I am working on.
I know it is not called because I set a cookie, and in my content script on that iframe it is always unset. As well as that, manual console.log() debugging shows that it is never called.

rgleeson@: Thanks for the update, please let us know if there is a reproducible steps if its a real issue to further investigate it, else let us know if we can close it.

Hi,
It's still an issue for me, but I haven't reproduced a smaller testcase yet.

Thank you for providing more feedback. Adding requester "durga.behera@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Thanks for the update, please update the thread once its ready to further investigate it.

Hi.

It's not an issue, really. The problem is just that without third party cookies enabled, `document.cookie` is absent of a value in an iframe.

Actually, the problem I wanted to solve was to have a method to ask for settings from background page without being forced to being asynchronous, because my content script is available at "document_start", and going async lets other code run, when I really have to read the settings before letting this happen.

It's a very specific case.
Should I open a new issue for this?

Thank you for providing more feedback. Adding requester "durga.behera@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot