Description of the issue:
The new update, changed all the bookmark folder icons to be:
This has made it a little more bland and hard to separate the folders at a glance
Since the icon are the same color as the text now, everything kind of blends together
This wasn’t the case prior, when a very visible yellow folder separated them
CURRENT:
OLD:
Expected result:
Ability to go back to the default folder icon:
Brave Version:
2 Likes
bump. I want to know if there’s an answer for this as well
1 Like
There is no way to opt out of the new design. You can open a feature request on Github, that way developers will be aware of your wish for such an option.
P.S It looks like other Brave users also want an option to choose the bookmarks icon.
brave:master ← brave:bookmarks_bar_folder_image
opened 01:18AM - 14 Jul 21 UTC
Resolves https://github.com/brave/brave-browser/issues/16940
Windows:
macOS:
<img width="240" alt="Screen Shot 2021-07-14 at 10 38 06 AM" src="https://user-images.githubusercontent.com/6786187/125546970-510de16f-6f5f-4fc4-abec-614ba3576758.png">
<img width="212" alt="Screen Shot 2021-07-14 at 10 38 16 AM" src="https://user-images.githubusercontent.com/6786187/125546974-d15c1afb-7702-4206-9610-cefbb454a81f.png">
Linux:
## Submitter Checklist:
- [x] I confirm that no security/privacy review [is needed](https://github.com/brave/brave-browser/wiki/Security-reviews), or that I have [requested](https://github.com/brave/security/issues/new/choose) one
- [x] There is a [ticket](https://github.com/brave/brave-browser/issues) for my issue
- [x] Used Github [auto-closing keywords](https://docs.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue) in the PR description above
- [x] Wrote a good [PR/commit description](https://google.github.io/eng-practices/review/developer/cl-descriptions.html)
- [x] Added appropriate labels (`QA/Yes` or `QA/No`; `release-notes/include` or `release-notes/exclude`; `OS/...`) to the associated issue
- [ ] Checked the PR locally: `npm run test -- brave_browser_tests`, `npm run test -- brave_unit_tests`, `npm run lint`, `npm run gn_check`, `npm run tslint`
- [x] Ran `git rebase master` (if needed)
## Reviewer Checklist:
- [ ] A security review [is not needed](https://github.com/brave/brave-browser/wiki/Security-reviews), or a link to one is included in the PR description
- [ ] New files have MPL-2.0 license header
- [ ] Adequate test coverage exists to prevent regressions
- [ ] Major classes, functions and non-trivial code blocks are well-commented
- [ ] Changes in component dependencies are properly reflected in `gn`
- [ ] Code follows the [style guide](https://chromium.googlesource.com/chromium/src/+/HEAD/styleguide/c++/c++.md)
- [ ] Test plan is specified in PR before merging
## After-merge Checklist:
- [ ] The associated issue milestone is set to the smallest version that the
changes has landed on
- [ ] All relevant documentation has been updated, for instance:
- [ ] https://github.com/brave/brave-browser/wiki/Deviations-from-Chromium-(features-we-disable-or-remove)
- [ ] https://github.com/brave/brave-browser/wiki/Proxy-redirected-URLs
- [ ] https://github.com/brave/brave-browser/wiki/Fingerprinting-Protections
- [ ] https://github.com/brave/brave-browser/wiki/Brave%E2%80%99s-Use-of-Referral-Codes
- [ ] https://github.com/brave/brave-browser/wiki/Custom-Headers
- [ ] https://github.com/brave/brave-browser/wiki/Web-Compatibility-Exceptions-in-Brave
- [ ] https://github.com/brave/brave-browser/wiki/QA-Guide
- [ ] https://github.com/brave/brave-browser/wiki/P3A
## Test Plan:
1 Like
Submitted. Thanks for the direction!
Yeah, It makes sense others are not liking it. Its a big visual difference when you utilize them a lot. I get that the minimalistic look is the thing now, but sometimes applying it overall isn’t the best.
Also as a web dev, giving the user the option, via toggles, is always nice!
I don’t want to have to just go back to chrome, or another chromium build that has the basic folders XD, but if they remain I probably will, in the long run, to be honest.
2 Likes
AlanRC
August 12, 2021, 6:51pm
5
Smokey, you hit the nail on the head perfectly. I have the same issue. The new folder icon in the bookmarks bar is NOT an improvement over the old one. I really hate change for the sake of change, and the new icon just disappears into the background. The option to return to the old one would be wonderful.
2 Likes
Ditto. It’s horrible, makes the individual bookmarks hard to see, especially with 70 year old eyes. Can’t imagine how anyone could think it is a better presentation.
1 Like
OP opened the following Github issue:
opened 05:19PM - 12 Aug 21 UTC
OS/Desktop
I am a web developer, and I manage different clients in my bookmark folders.
- … The new update, changed all the bookmark folder icons to be: 
- This has made it a little more bland and hard to separate the folders at a glance
- Since the icon are the same color as the text now, everything kind of blends together
- This wasn't the case prior, when a very visible yellow folder separated them
CURRENT:
OLD:
**Expected result:**
Ability to go back to the default folder icon: 
**Brave Version:**
Version 1.28.105 Chromium: 92.0.4515.131 (Official Build) (64-bit)
Feel free to voice your opinion over there so developers can see your issues with the new design.
I read that v129 nightly would add an option to deal with this.
BTW, EVEN GOOGLE ALLOWED USERS TO GO BACK! TO YELLOW FOLDER ICONS ON CHROME!!!
