Closed
Bug 1043928
Opened 10 years ago
Closed 9 years ago
[User Story] Manually expand Browser Chrome
Categories
(Firefox OS Graveyard :: Gaia::System::Browser Chrome, defect, P2)
Firefox OS Graveyard
Gaia::System::Browser Chrome
Tracking
(feature-b2g:2.5+, tracking-b2g:backlog)
RESOLVED
FIXED
People
(Reporter: benfrancis, Assigned: benfrancis)
References
Details
(Keywords: feature, uiwanted, Whiteboard: [systemsfe][p=3])
User Story
As a user I want to manually expand the browser chrome on any window so that I can access browser chrome even if the current site is pinned and/or the current page does not scroll. As a user I want to manually collapse the browser chrome so that I can hide it even if the current site is not pinned and/or the current page does not scroll. Previous interaction spec: https://mozilla.app.box.com/s/4pfp6y8pjhwojtt9yhl8/1/2243605137/19330716869/1
Attachments
(2 files)
Bug 1039519 tracks expanding & collapsing Rocketbar indirectly by scrolling a browser frame in the new Rocketbar implementation.
This bug tracks the new requirement to directly expand/collapse the Rocketbar by tapping and swiping it.
* Tapping a collapsed Rocketbar in an app without browser chrome should transition directly to the expanded focused state (this is covered in bug 1043284)
* Tapping a collapsed Rocketbar in a browser window or an app window with browser chrome should transition the Rocketbar to an expanded, unfocused state and display any necessary browser chrome.
* Swiping up on an expanded, unfocused Rocketbar should collapse it.
Comment 1•10 years ago
|
||
Since we have removed the swipe to show/hide the rocketbar I believe this can now be closed. Go scrollgrab!
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
Assignee | ||
Comment 2•10 years ago
|
||
I think it's highly likely that we're going to need a mechanism to do this in the future.
Scrollgrab only works for scrollable web pages and not being able to collapse the Rocketbar for non-scrollable apps like Google Maps is quite annoying. It's also not very satisfying that I can't collapse the Rocketbar in the Facebook app without scrolling down the page. We may also find weird cases where it is possible to collapse the Rocketbar but not be able to expand it again.
Unblocking the MVP bug because we can do this in a future release, but I would like to keep this bug open.
Updated•10 years ago
|
Blocks: rocketbar-next
Updated•10 years ago
|
blocking-b2g: --- → backlog
feature-b2g: --- → 2.2?
Updated•10 years ago
|
User Story: (updated)
Updated•10 years ago
|
Priority: -- → P2
Updated•10 years ago
|
Assignee: nobody → dale
Updated•10 years ago
|
feature-b2g: 2.2? → ---
Updated•10 years ago
|
blocking-b2g: backlog → ---
tracking-b2g:
--- → backlog
Assignee | ||
Comment 4•9 years ago
|
||
Updating for Pin the Web.
Francis, as per the Pin the Web prototype I think we can expand the browser chrome with a tap (second tap focuses the URL bar), but do we also need a way to manually collapse it again?
Blocks: pin-the-web
User Story: (updated)
Flags: needinfo?(fdjabri)
Summary: [User Story] Manually expand/collapse Rocketbar → [User Story] Manually expand/collapse Browser Chrome
Comment 5•9 years ago
|
||
We could just collapse it again when you touch the browser frame? (I'd say on scroll, but this will break on pages that aren't scrollable)
Updated•9 years ago
|
feature-b2g: --- → 2.5+
Comment 6•9 years ago
|
||
Assignee | ||
Comment 7•9 years ago
|
||
Added WIP patch, currently depends on the patch from bug 1168951.
Assignee | ||
Updated•9 years ago
|
Assignee: nobody → bfrancis
Assignee | ||
Comment 8•9 years ago
|
||
Assignee | ||
Comment 9•9 years ago
|
||
Splitting out manually collapsing browser chrome to a separate bug, bug 1192010 until we have a spec for that.
Flags: needinfo?(fdjabri)
Summary: [User Story] Manually expand/collapse Browser Chrome → [User Story] Manually expand Browser Chrome
Assignee | ||
Comment 10•9 years ago
|
||
Comment on attachment 8642587 [details]
[gaia] benfrancis:1043928 > mozilla-b2g:master
Alberto, if you could review this in time for us to get it landed before sprint planning on Monday that would be awesome :D
Attachment #8642587 -
Flags: review?(apastor)
Comment 11•9 years ago
|
||
Comment on attachment 8642587 [details]
[gaia] benfrancis:1043928 > mozilla-b2g:master
r=me with a small comment in Github. Thanks!
Attachment #8642587 -
Flags: review?(apastor) → review+
Assignee | ||
Comment 12•9 years ago
|
||
Thanks Alberto (weekend code reviews are beyond the call of duty!), I think your comment on the unit test is covered so I've gone ahead and landed this. Please file a follow-up if I was mistaken!
https://github.com/mozilla-b2g/gaia/commit/246c8f18a5af4a8333be2f75dd8453a4cb975f7d
Status: REOPENED → RESOLVED
Closed: 10 years ago → 9 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•