Closed Bug 412209 Opened 17 years ago Closed 16 years ago

Support full screen mode in prism webapps

Categories

(Mozilla Labs :: Prism, enhancement)

x86
Linux
enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: luis, Assigned: tonikitoo)

References

Details

Attachments

(1 file, 5 obsolete files)

Would be nice if prism respected the keyboard command for view->full screen so that prism apps could be used in a full screen mode.
Summary: full screen → Support full screen mode
Assignee: nobody → tonikitoo
Attachment #338557 - Flags: review?(mark.finkle)
Summary: Support full screen mode → Support full screen mode in prism webapps
Attachment #338557 - Flags: review?(mark.finkle) → review?(matthew.gertner)
Comment on attachment 338557 [details] [diff] [review] add fullscreen support in webapps Couldn't we store the fullscreen setting in the JSON file too? We could just use a different value and treat it as a window state. Also, I think the sidebar block should be outside the "else" block. The sidebar should be respected regardless of fullscreen, right?
Attached patch v0.2 - integrated to json (obsolete) — Splinter Review
> Couldn't we store the fullscreen setting in the JSON file too? We could just > use a different value and treat it as a window state. done. > Also, I think the sidebar block should be outside the "else" block. The sidebar > should be respected regardless of fullscreen, right? no need after step above.
Attachment #338557 - Attachment is obsolete: true
Attachment #338856 - Flags: review?(mark.finkle)
Attachment #338557 - Flags: review?(matthew.gertner)
Attached patch v0.3 (obsolete) — Splinter Review
indentation changed accidentally. see comment #3 for description
Attachment #338856 - Attachment is obsolete: true
Attachment #338858 - Flags: review?(mark.finkle)
Attachment #338856 - Flags: review?(mark.finkle)
Comment on attachment 338858 [details] [diff] [review] v0.3 Why do we need the ui.fullscreen pref? Won't the normal load/saveSettings methods remember the fullscreen state and restore it if necessary (with a bit of additional code in those methods). Also, I think that the full screen constant should be a global const value, not a member variable: const FULL_SCREEN_STATE_MASK = 0x4;
Attached patch v0.4 (obsolete) — Splinter Review
addressed comments from matthew and mark.
Attachment #338858 - Attachment is obsolete: true
Attachment #338951 - Flags: review?
Attachment #338858 - Flags: review?(mark.finkle)
Attachment #338951 - Attachment description: v3 → v0.4
Attachment #338951 - Flags: review? → review?(mark.finkle)
Attached patch simpler approach (obsolete) — Splinter Review
Attachment #338951 - Attachment is obsolete: true
Attachment #338971 - Flags: review?(mark.finkle)
Attachment #338951 - Flags: review?(mark.finkle)
Comment on attachment 338971 [details] [diff] [review] simpler approach nice
Attachment #338971 - Flags: review?(mark.finkle) → review+
Keywords: checkin-needed
un-bitrotted patch. checking re-ping.
Attachment #338971 - Attachment is obsolete: true
Completed: At revision: 19012
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Attachment #342709 - Attachment description: simpler approach - (unbitrotted) → simpler approach - (unbitrotted) [Checkin: Comment 10]
Blocks: 450333
How about a --fullscreen command-line option?
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: