Skip to content
This repository has been archived by the owner on Feb 26, 2022. It is now read-only.

bug 796917 using postMessage to an iframe from a content script does not serialize data #647

Merged
merged 2 commits into from Nov 5, 2012

Conversation

erikvold
Copy link
Contributor

@erikvold erikvold commented Nov 2, 2012

No description provided.

jscode += JSON.stringify(message);
else
jscode += "'" + message.toString().replace(/['\\]/g,"\\$&") + "'";

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe we should have a function for that.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I can't require in to this file I think, it's only used in this one spot atm, which is mostly a isolated function, it just does the eval afterewards too. So I'm just going to leave this for now, hopefully we can remove all of this code soon too.

@Gozala
Copy link
Contributor

Gozala commented Nov 5, 2012

@ochameau What happened with removal of content-proxy ? Is there anything blocking us from doing it ?

erikvold added a commit that referenced this pull request Nov 5, 2012
fix bug 796917 using postMessage to an iframe from a content script does not serialize data r=@Gozala
@erikvold erikvold merged commit 2f4f95b into mozilla:master Nov 5, 2012
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
2 participants