Closed Bug 1138566 Opened 11 years ago Closed 11 years ago

Camera API ApiRef Macro TemplateExecutionError

Categories

(Developer Documentation Graveyard :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: brad, Unassigned)

Details

Attachments

(1 file)

Attached image Screenshot of the error
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:38.0) Gecko/20100101 Firefox/38.0 Build ID: 20150228155808 Steps to reproduce: 1. Go to https://developer.mozilla.org/en-US/docs/Web/API/CameraCapabilities/flashModes 2. Preview changes (even without editing) Actual results: An error appears: Error type: TemplateExecutionError In macro: ApiRef (Edit Template) Parsing macro: ApiRef([u'Camera API']) Full text of error: Expected results: No errors, as nothing changed. (For background, wanted to suggest editing the "This API is available on Firefox OS for internal applications only." notice, because as of 2.0 this isn't the case anymore.)
The page has been regenerated. The error has gone. cc/ Chris who is maintaining the Firefox OS docs.
(In reply to brad from comment #0) > > (For background, wanted to suggest editing the "This API is available on > Firefox OS for internal applications only." notice, because as of 2.0 this > isn't the case anymore.) Good spot Brad - the Camera API is now available to internal and priviledged. I've updated all the macros to say this.
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Chris: what's the current process to catch these changes? Do the dev teams open a bug for such a change or is it done outside the bugzilla realm?
Flags: needinfo?(cmills)
Usually I see announcements on lists like dev-webapi or dev-b2g, sometimes a bug is filed. In this particular case I saw the annoucement and did most of the work required to communicate this on MDN, but overlooked updating these banners. I guess the normal process should be to file a bug? Should we reiterate this to the engineers with a mail out?
Flags: needinfo?(cmills)
I have similar issues at the english and german version of the WindowTimers.setTimeout() page https://developer.mozilla.org/en-US/docs/Web/API/WindowTimers/setTimeout
(In reply to Egon Steiner from comment #5) > I have similar issues at the english and german version of the > WindowTimers.setTimeout() page > https://developer.mozilla.org/en-US/docs/Web/API/WindowTimers/setTimeout Still, they look ok now.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: