Closed Bug 903434 Opened 12 years ago Closed 7 years ago

Fullscreen app manifest property should be using direct booleans, not strings

Categories

(Firefox OS Graveyard :: Gaia, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: jsmith, Unassigned)

Details

(Keywords: dev-doc-complete)

Per the discussion on bug 903165, the app manifest spec wants direct booleans used, not strings, to define boolean-based values. As a result, the fullscreen app manifest property is currently implemented incorrectly - it should be using true instead of "true."
Agreed. We can keep compat with the old syntax if we really need to by simply checking the type (string vs. boolean)
I changed the fullscreen docs to use a true boolean: https://developer.mozilla.org/en-US/docs/Web/Apps/Manifest#fullscreen
(In reply to Mark Giffin [:markg] from comment #3) > I changed the fullscreen docs to use a true boolean: > > https://developer.mozilla.org/en-US/docs/Web/Apps/Manifest#fullscreen Looks like it has been reverted back to a string: https://developer.mozilla.org/en-US/Apps/Build/Manifest#fullscreen
It looks like the reason the documentation is using a string for fullscreen instead of a boolean is because the packaged app validator (and probably Firefox OS) also requires it to be a string (which is of course a bug).
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.