This repository has been archived by the owner on Dec 11, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 975
Bookmark bar stays visible after all bookmarks are deleted #14047
Labels
Milestone
Comments
btlechowski
added
feature/bookmarks
regression
0.22.x-single-webview
Issue first seen on single-webview build against v0.22.x branch
labels
May 7, 2018
Note that this is also sort of reproducible in the current release, except that in the current release, the bookmarks toolbar gets really short, which itself was considered a bug since a user could not have the bookmarks toolbar with normal height with no bookmark items in order to interact with it. |
petemill
removed
regression
0.22.x-single-webview
Issue first seen on single-webview build against v0.22.x branch
labels
May 8, 2018
petemill
added a commit
that referenced
this issue
May 8, 2018
Fix #14047 The bookmark bar has always remained 'visible' when removing the last item. It just happened to be reduced to a few pixels tall. This was a defect as it affected the vertical rhythm of the UI. With #13758, the toolbar always remains the set height. With this change, the toolbar is hidden automatically when the last item is removed, just like it already automatically shows when the first item is added. Test Plan: Automated - `npm run unittest -- --grep 'bookmarksReducer'` Manual - Add several bookmark items, including folders - Remove some items - observe the toolbar is still shown - Move some items - observe the toolbar is still shown - Delete all items - observe the toolbar is not shown anymore - Recreate items, and use 'move' to put all items in a folder that is not on the bookmark bar - observe the toolbar is not shown anymore
10 tasks
petemill
added a commit
that referenced
this issue
May 8, 2018
Fix #14047 The bookmark bar has always remained 'visible' when removing the last item. It just happened to be reduced to a few pixels tall. This was a defect as it affected the vertical rhythm of the UI. With #13758, the toolbar always remains the set height. With this change, the toolbar is hidden automatically when the last item is removed, just like it already automatically shows when the first item is added. Test Plan: Automated - `npm run unittest -- --grep 'bookmarksReducer'` Manual - Add several bookmark items, including folders - Remove some items - observe the toolbar is still shown - Move some items - observe the toolbar is still shown - Delete all items - observe the toolbar is not shown anymore - Recreate items, and use 'move' to put all items in a folder that is not on the bookmark bar - observe the toolbar is not shown anymore
petemill
added a commit
that referenced
this issue
May 8, 2018
Fix #14047 The bookmark bar has always remained 'visible' when removing the last item. It just happened to be reduced to a few pixels tall. This was a defect as it affected the vertical rhythm of the UI. With #13758, the toolbar always remains the set height. With this change, the toolbar is hidden automatically when the last item is removed, just like it already automatically shows when the first item is added. Test Plan: Automated - `npm run unittest -- --grep 'bookmarksReducer'` Manual - Add several bookmark items, including folders - Remove some items - observe the toolbar is still shown - Move some items - observe the toolbar is still shown - Delete all items - observe the toolbar is not shown anymore - Recreate items, and use 'move' to put all items in a folder that is not on the bookmark bar - observe the toolbar is not shown anymore
btlechowski
added
QA/test-plan-specified
QA/checked-Linux
and removed
PR/pending-review
labels
May 9, 2018
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
Steps to Reproduce
Actual result:
Bookmark bar stays visible
Expected result:
Bookmark bar is hidden
Reproduces how often:
100%
Brave Version
Also reproduced on Mac and Windows by @srirambv @LaurenWags @kjozwiak
Reproducible on current live release:
No. Tested v0.22.669
Cc @bsclifton @petemill
The text was updated successfully, but these errors were encountered: