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

Please mention issue #4 in documentation #81

Closed
marnen opened this issue Jul 2, 2012 · 4 comments
Closed

Please mention issue #4 in documentation #81

marnen opened this issue Jul 2, 2012 · 4 comments

Comments

@marnen
Copy link

marnen commented Jul 2, 2012

Issue #4 describes a major "gotcha". It was suggested 2 years ago that this be put into the README, but that was never done -- and it just cost me lots of debugging time.

I'll submit a pull request for the updated docs if I get a few minutes, but meanwhile I'm opening this issue.

@travisjeffery
Copy link
Collaborator

Sure, make the pull request.

@Sequoia
Copy link
Contributor

Sequoia commented Jul 20, 2012

@marnen Puuuuuuull request! :)

@marnen
Copy link
Author

marnen commented Jul 20, 2012

Sorry, been too busy to get to this. Thanks for the reminder: I'll see what I can do.

@travisjeffery
Copy link
Collaborator

Actually seems like this is already covered in "Cross domain policy problems under Chrome" section of the README.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants