Closed
Bug 795044
Opened 13 years ago
Closed 12 years ago
Access MDN documentation in-browser with JavaScript
Categories
(developer.mozilla.org Graveyard :: Collaboration, defect)
developer.mozilla.org Graveyard
Collaboration
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 720068
People
(Reporter: thomasmitchellanderson, Unassigned)
References
Details
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_4) AppleWebKit/537.1 (KHTML, like Gecko) Chrome/21.0.1180.89 Safari/537.1
Steps to reproduce:
Tried accessing MDN documentation with JavaScript (via CORS) and through a frame.
Actual results:
MDN disallows frames, and will not allow cross-domain requests.
Expected results:
I should, in someway, have been able to access the MDN documentation for use in a web application.
Comment 1•13 years ago
|
||
Thanks for the report Thomas! Can you let me know what endpoint you tried to hit? Do you have a small sample HTML / JS file you could give me to see how you're trying to access MDN?
Comment 2•13 years ago
|
||
I don't think we have CORS headers turned on for the new wiki yet, but we need to do so. We're not intentionally blocking.
https://bugzilla.mozilla.org/show_bug.cgi?id=720068
Depends on: 720068
| Reporter | ||
Comment 3•13 years ago
|
||
@David
I wasn't using any of the existing APIs -- I was just trying to access MDN in some way from a client-side application. I had tried frames and cross-domain xmlhttp requests, and neither was in place to work. It looks like Les pointed this in the right direction.
@Les
Ah, I'd never think Mozilla would intentionally block anything internet related! Thanks for pointing me to that other ticket.
So, yes. I was basically questioning whether (or requesting that) either CORS be allowed for the MDN api or just for accessing the wiki pages in general.
Updated•12 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
Updated•6 years ago
|
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•