Closed Bug 435894 Opened 16 years ago Closed 8 years ago

dragevents.html example code doesn't work: error message not allowed to read XPCComponents.classes

Categories

(Developer Documentation Graveyard :: Mozilla Platform, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: no-reply-address-of-florian, Unassigned)

References

()

Details

(Whiteboard: c=Platform u=mozdev p=0)

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9) Gecko/2008051202 Firefox/3.0
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9) Gecko/2008051202 Firefox/3.0

The example:
http://developer.mozilla.org/samples/dragdrop/dragevents.html
from:
http://developer.mozilla.org/en/docs/Drag_and_drop_events
doesn't work.

an error "not allowed to read property Components.classes" (translated from german) appear at line 6:
var dragService = Components.classes["@mozilla.org/widget/dragservice;1"].
                    getService(nsIDragService);

Reproducible: Always

Steps to Reproduce:
1.
2.
3.
Well, https://developer.mozilla.org/en/Drag_and_Drop does say that this API is for chrome (extensions) only, but https://developer.mozilla.org/en/Drag_and_drop_events , which links to the example, indeed doesn't mention that and is generally messed up.
Component: General → Documentation Requests
Product: Firefox → Mozilla Developer Center
QA Contact: general → doc-request
Summary: Example code doesn't work: error message not allowed to read XPCComponents.classes → dragevents.html example code doesn't work: error message not allowed to read XPCComponents.classes
Component: Documentation Requests → Documentation
Component: Documentation → General
Product: Mozilla Developer Network → Developer Documentation
Whiteboard: u=mozdev p=0
Component: General → Mozilla Platform
Whiteboard: u=mozdev p=0 → c=Platform u=mozdev p=0
This page has been archived long ago.
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.