The default bug view has changed. See this FAQ.

Notes on usage of document.domain missing one important thing



Developer Documentation
9 years ago
4 years ago


(Reporter: Peter Kehl, Assigned: sheppy)





(1 attachment)



9 years ago
Created attachment 320712 [details]
Example to test cross-domain JS with document.domain

Hi, would you consider adding the following section to the bottom of the page. See also the attached package, which I used to test in Firefox on Mac OS X. When I didn't set document.domain in the higher (parent) domain, then I was still getting permission errors.

Note that you need to  set <i>document.domain</i> in both the subdomain and the parent domain to the same value. You need to do that
even when setting document.domain in the parent domain to its 'native' (original) domain. It's not enough to set it only on the subdomain part. Otherwise you'd still get permission errors.
Product: → Websites
Component: Other →
Product: Websites →
QA Contact: other → www-mozilla-org
Version: unspecified → other

Comment 1

9 years ago
This page had been moved over to MDC but a redirect was missing.  I just set a redirect up to the correct page at

Changing product to Mozilla Developer Center to discuss original issue of adding additional information to the page.
Component: → Documentation Requests
Product: Websites → Mozilla Developer Center
QA Contact: www-mozilla-org → doc-request
Version: other → unspecified
Component: Documentation Requests → Documentation
Product: Mozilla Developer Network → Mozilla Developer Network
Component: Documentation → General
Product: Mozilla Developer Network → Developer Documentation

Comment 2

4 years ago
Updated the article.
Assignee: nobody → eshepherd
Last Resolved: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.