Closed Bug 1088723 Opened 10 years ago Closed 9 years ago

Status bar visible while handling pick activity with Camera

Categories

(Firefox OS Graveyard :: Gaia::System::Window Mgmt, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(tracking-b2g:backlog, b2g-v2.1 wontfix, b2g-v2.2 fixed, b2g-master fixed)

RESOLVED FIXED
2.2 S5 (6feb)
tracking-b2g backlog
Tracking Status
b2g-v2.1 --- wontfix
b2g-v2.2 --- fixed
b2g-master --- fixed

People

(Reporter: gerard-majax, Assigned: mancas)

References

Details

(Keywords: polish, regression, Whiteboard: [systemsfe])

Attachments

(1 file)

Reproduced on current master, with Flame KK and Nexus S.

STR:
 0. Open SMS app
 1. Compose new message
 2. Tap attachment, select Photo/Camera

Expected:
 Taking picture, no statusbar visible.

Actual:
 Taking picture, but the statusbar is visible.
Flags: needinfo?(firefoxos-ux-bugzilla)
Believe status bar should be visible. Checking with Katie.
Flags: needinfo?(firefoxos-ux-bugzilla) → needinfo?(kcaldwell)
(In reply to Stephany Wilkes from comment #1)
> Believe status bar should be visible. Checking with Katie.

As far as I remember, we were hiding statusbar previously for this usecase. And Android does too. Having a statusbar there is quite misleading (not to mention that we have perf issues on this topic, I remember Vivien working on this for the utility tray).
The camera, when accessed via SMS, should follow the same behaviour as camera app itself. The status bar is not visible by default, but can be activated by dragging from the top edge.
Flags: needinfo?(kcaldwell)
(In reply to katieC from comment #3)
> The camera, when accessed via SMS, should follow the same behaviour as
> camera app itself. The status bar is not visible by default, but can be
> activated by dragging from the top edge.

So there's clearly a bug, since we see the statusbar always, not just when dragging it.
Assignee: nobody → b.mcb
Attached file No status bar - patch
This is a first approach to solve this bug. Please let me know any change we should implement to improve the solution.

Thanks!
Attachment #8513307 - Flags: review?(timdream)
Comment on attachment 8513307 [details] [review]
No status bar - patch

Alive should review this, but I hardly thinks hardcoding the origin of Camera app is the right solution.
Attachment #8513307 - Flags: review?(timdream) → review?(alive)
Comment on attachment 8513307 [details] [review]
No status bar - patch

Bad.
If we want to implement this feature, what we should do is control the "statusbar shadow" part in activityWindow: if we are fullscreen activity judging from manifest, we may need to hide the shadow statusbar on init. Or even don't render it.
https://github.com/mozilla-b2g/gaia/blob/master/apps/system/js/app_window.js#L511
Attachment #8513307 - Flags: review?(alive) → review-
Alive, the decission about if the activity is fullscreen or not, gives priority to the parent app:

this._fullscreen = this.rearWindow ?
                   this.rearWindow.isFullScreen() :
                   this.manifest ?
                   !!this.manifest.fullscreen :
                   false;

What you said about the |statusbar-shadow|, AFAIK, doesn't hide the status bar. If we want to prioritize the fullscreen mode from the child activity, we should change the order of the previous code. Could you clarify this, please?
Flags: needinfo?(alive)
(In reply to Manuel Casas Barrado [:mancas] from comment #8)
> Alive, the decission about if the activity is fullscreen or not, gives
> priority to the parent app:
> 
> this._fullscreen = this.rearWindow ?
>                    this.rearWindow.isFullScreen() :
>                    this.manifest ?
>                    !!this.manifest.fullscreen :
>                    false;
> 
> What you said about the |statusbar-shadow|, AFAIK, doesn't hide the status
> bar. If we want to prioritize the fullscreen mode from the child activity,
> we should change the order of the previous code. Could you clarify this,
> please?

Apparent it is not designed to use the original fullscreen property because long time ago statusbar is not working with AppWindow well and we are not requested to do that. Now since you want to change the behavior, please fix that function.
Note: this is a feature request. We should be careful about any regressions.
Flags: needinfo?(alive)
Adding a reference to bug 1090152, seems likely that the same patch could regress both of these.
See Also: → 1090152
blocking-b2g: 2.2? → backlog
Keywords: polish
Putting it in front of the polish team's eyes.
Whiteboard: [systemsfe]
Per comment #10, is this bug still relevant?
Flags: needinfo?(b.mcb)
I still see the issue on my build that is a couple of days old ...
Comment on attachment 8513307 [details] [review]
No status bar - patch

Alive, I've modified the function that handle the fullscreen mode. Now, the function prioritizes the fullscreen mode of the activity that is going to be opened, but using the fullscreen mode of its parent app, if the fullscreen mode in the manifest is not defined.

Could you review it when you get a chance?
Thanks!
Flags: needinfo?(b.mcb)
Attachment #8513307 - Flags: review- → review?(alive)
Comment on attachment 8513307 [details] [review]
No status bar - patch

LGTM, thank you Mancas.
Attachment #8513307 - Flags: review?(alive) → review+
Manuel, please request v2.2 uplift when you get the chance.
Flags: needinfo?(b.mcb)
Comment on attachment 8513307 [details] [review]
No status bar - patch

[Approval Request Comment]
[Bug caused by] (feature/regressing bug #): Activity Window
[User impact] if declined: The status bar will be visible in fullscreen apps, camera per example, when it's opened from another app.
[Testing completed]: Yes
[Risk to taking this patch] (and alternatives if risky): Low
[String changes made]: No
Flags: needinfo?(b.mcb)
Attachment #8513307 - Flags: approval-gaia-v2.2?
Attachment #8513307 - Flags: approval-gaia-v2.2? → approval-gaia-v2.2+
blocking-b2g: backlog → ---
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: