Closed
Bug 790023
Opened 12 years ago
Closed 4 years ago
Many pages on MDN still mention enablePrivilege
Categories
(Developer Documentation Graveyard :: Mozilla Platform, defect, P5)
Developer Documentation Graveyard
Mozilla Platform
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: jruderman, Unassigned)
Details
enablePrivilege has been removed: https://developer.mozilla.org/en-US/docs/Bypassing_Security_Restrictions_and_Signing_Code But there are many other hits for enablePrivilege on MDN: * https://developer.mozilla.org/en-US/search?q=enablePrivilege * https://www.google.com/search?q=enableprivilege%20site:developer.mozilla.org%20-revision%20-revisions For code snippets that are intended to run as part of an add-on, the call to enablePrivilege can just be removed.
Reporter | ||
Comment 1•12 years ago
|
||
Oh, MDN search *is* Google search. In that case: https://developer.mozilla.org/en-US/search?q=enablePrivilege+inurl%3Aen-US+-revision+-revisions (working around bug 790027)
Comment 2•12 years ago
|
||
You can remove the references to 'enablePrivilege' by clicking the "Edit" button at the top-right of the page. ;)
Component: Website → Documentation Requests
Assignee | ||
Updated•12 years ago
|
Component: Documentation Requests → Documentation
Updated•12 years ago
|
Component: Documentation → General
Product: Mozilla Developer Network → Developer Documentation
Updated•11 years ago
|
Assignee: nobody → eshepherd
Component: General → Security
Keywords: dev-doc-needed
Priority: -- → P1
Whiteboard: u=webdev p=0
Updated•11 years ago
|
Whiteboard: u=webdev p=0 → u=webdev p=3 c=Security
Updated•7 years ago
|
Assignee: eshepherd → nobody
Component: Security → Mozilla Platform
Priority: P1 → P5
Whiteboard: u=webdev p=3 c=Security
Comment 3•4 years ago
|
||
MDN Web Docs' bug reporting has now moved to GitHub. From now on, please file content bugs at https://github.com/mdn/sprints/issues/ and platform bugs at https://github.com/mdn/kuma/issues/.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•