Skip to content
This repository has been archived by the owner on Dec 11, 2019. It is now read-only.

General Settings: "A new tab shows" setting #2106

Closed
bradleyrichter opened this issue Jun 7, 2016 · 15 comments · Fixed by #5301
Closed

General Settings: "A new tab shows" setting #2106

bradleyrichter opened this issue Jun 7, 2016 · 15 comments · Fixed by #5301

Comments

@bradleyrichter
Copy link
Contributor

bradleyrichter commented Jun 7, 2016

Functionality:
"my new tab page"

  • shows the current version of a new tab page (blank white at time of writing)

"my home page"

  • shows the currently defined home page

"my default search engine"

  • shows the home page of the currently set default search engine

Item label:
"A new tab shows"

Menu choices:
"my new tab page"
"my home page"
"my default search engine"

menu snapshot:
image

Settings panel: (item for this issue shown in blue)
image

@kingscott
Copy link

Any chance this has been taken on? I just started the early stages of writing something of this sort. Any chance I could work on it or collaborate? @bradleyrichter

@bradleyrichter
Copy link
Contributor Author

@kingscott We'd love to have your help!

This has not been started yet, besides what is currently implemented in today's release in the general prefs panel which is limited to startup, not a new tab view.

For code review, we can ask @bridiver or @bbondy .

@kingscott
Copy link

Great, thanks @bradleyrichter! I was jumping into it today at the end of my work day. Is that settings panel mentioned in the above image what has been agreed upon for production?

@bradleyrichter
Copy link
Contributor Author

Hey @kingscott - I just updated it for you. But, please don't bother with the visual elements because we are currently working on a branch which is a complete prefs makeover.

We will have to merge your new code with the new UI work. Shouldn't be a problem...

If you want to take a look at the progress on that branch, here it is:

https://github.com/brave/browser-laptop/tree/cherry-picked-ui-updates

@bradleyrichter
Copy link
Contributor Author

I’m all ears…

On Jun 27, 2016, at 10:45 AM, Scott King notifications@github.com wrote:

Hey @bradleyrichter https://github.com/bradleyrichter, just a quick opinion question for functionality. I have had a few ideas for this new tab stuff


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub #2106 (comment), or mute the thread https://github.com/notifications/unsubscribe/AM4jqqe4dYkyn7p1B_btu1xRt1rq8jq2ks5qQAwxgaJpZM4Ivb8W.

@kingscott
Copy link

Sorry about that, I had thought and didn't mean to write the comment (was trying to overcomplicate the task).

Also, did you want (or need) the new tab page created that has the tiles of previously visited pages?

@bradleyrichter
Copy link
Contributor Author

@kingscott We would love the help on anything you are interested in working on. Here is a screen shot of the currently proposed "Top Sites/Info Page" but I haven't finished the details in the spec.

image

When you mouse-hover over the topsite thumbs, you would get the full page preview rendered behind the shadow masking:

image

There will be a neat UI to change the layout of the top site icons by clicking on a toggle button to change from 1, 2 or 3 rows, and a list view.

Let me know if this looks interesting to you...

Thanks!
Brad

@kingscott
Copy link

kingscott commented Jun 28, 2016

Wow, that looks really nice! Honestly - the top image looks awesome. I tend to prefer the more neutral images for new tab stuff.

Is that something you (Brave) would want me to build? In terms of the background, I do have a project I worked on that pulls in nice backgrounds. I have a Chrome extension for it as well. If that was of interest, I can extend and/or integrate with Brave. PS. It's in React as well.

EDIT: Just re-read the comment for the second picture - so disregard my second comment in the top paragraph. Sounds truly great 👍

@bradleyrichter
Copy link
Contributor Author

Hey Scott - can I invite you to join our #community slack channel?

Also - I installed the chrome extension. Looks good. I think this is right up your alley. : )

@kingscott
Copy link

Sure, that would be great Brad!

@bradleyrichter bradleyrichter removed this from the 0.11.0dev milestone Jun 30, 2016
@bradleyrichter
Copy link
Contributor Author

@kingscott Just invited you as a contributor...

@kingscott
Copy link

Yes @bradleyrichter, I got it - thanks!

@bsclifton
Copy link
Member

Original work done in PR #3488

bsclifton pushed a commit that referenced this issue Oct 31, 2016
- Add settings for new tab behaviour, handle this behaviour when you click the new tab button
- Scaffolding for deafult search engine appearing as new tab
- Grab proper search engine information on new tab
- New tab can load default search engine
- New tab can load default search engine
- Add functionality for new tab options
- Abstraction of handling new tab settings
- Abstraction of handling new
- Hopefully final abstraction to complete new tab functionality
bsclifton added a commit that referenced this issue Oct 31, 2016
Fixes #2106

- pulled out setting values into an enum
- position moved to below "Brave starts with" (in preferences.js)
- resolved circular dependency issue in appUrlUtil which broke app
- made a newtab option called BLANK and renamed value TEMP. We can change back when ready to go live
- defaultUrl removed from main.js (since it gets defaulted in windowStore.js)
- removed defaultUrl from window.js (since windowStore.js also handles this)
- put about pages into config; updated contextMenus.js to use config constants
- adding missing "base" element to searchProviders that had it missing (mdn, github, startpage, etc)
- updated defaultUrl logic in appUrlUtil.js to default unknown values to about:blank
- windowStore.js now uses new defaultUrl method (from appUrlUtil) instead of config.defaultUrl

Auditors: @kingscott @cezaraugusto
bsclifton pushed a commit that referenced this issue Nov 1, 2016
- Add settings for new tab behaviour, handle this behaviour when you click the new tab button
- Scaffolding for deafult search engine appearing as new tab
- Grab proper search engine information on new tab
- New tab can load default search engine
- Add functionality for new tab options
- Abstraction of handling new tab settings
- Hopefully final abstraction to complete new tab functionality
bsclifton added a commit that referenced this issue Nov 1, 2016
Fixes #2106

- pulled out setting values into an enum
- position moved to below "Brave starts with" (in preferences.js)
- resolved circular dependency issue in appUrlUtil which broke app
- made a newtab option called BLANK and renamed value TEMP. We can change back when ready to go live
- defaultUrl removed from main.js (since it gets defaulted in windowStore.js)
- removed defaultUrl from window.js (since windowStore.js also handles this)
- put about pages into config; updated contextMenus.js to use config constants
- adding missing "base" element to searchProviders that had it missing (mdn, github, startpage, etc)
- updated defaultUrl logic in appUrlUtil.js to default unknown values to about:blank
- windowStore.js now uses new defaultUrl method (from appUrlUtil) instead of config.defaultUrl

Auditors: @kingscott @cezaraugusto
bsclifton pushed a commit that referenced this issue Nov 1, 2016
- Add settings for new tab behaviour, handle this behaviour when you click the new tab button
- Scaffolding for deafult search engine appearing as new tab
- Grab proper search engine information on new tab
- New tab can load default search engine
- Add functionality for new tab options
- Abstraction of handling new tab settings
- Hopefully final abstraction to complete new tab functionality
bsclifton added a commit that referenced this issue Nov 1, 2016
Fixes #2106

- pulled out setting values into an enum
- position moved to below "Brave starts with" (in preferences.js)
- resolved circular dependency issue in appUrlUtil which broke app
- made a newtab option called BLANK and renamed value TEMP. We can change back when ready to go live
- defaultUrl removed from main.js (since it gets defaulted in windowStore.js)
- removed defaultUrl from window.js (since windowStore.js also handles this)
- put about pages into config; updated contextMenus.js to use config constants
- adding missing "base" element to searchProviders that had it missing (mdn, github, startpage, etc)
- updated defaultUrl logic in appUrlUtil.js to default unknown values to about:blank
- windowStore.js now uses new defaultUrl method (from appUrlUtil) instead of config.defaultUrl

Auditors: @kingscott @cezaraugusto
bsclifton pushed a commit that referenced this issue Nov 1, 2016
- Add settings for new tab behaviour, handle this behaviour when you click the new tab button
- Scaffolding for deafult search engine appearing as new tab
- Grab proper search engine information on new tab
- New tab can load default search engine
- Add functionality for new tab options
- Abstraction of handling new tab settings
- Hopefully final abstraction to complete new tab functionality
bsclifton added a commit that referenced this issue Nov 1, 2016
Fixes #2106

Updated defaultUrl logic
- windowStore.js now uses new defaultUrl method (from appUrlUtil) instead of config.defaultUrl
- default unknown values to about:blank

Removed conflicting defaultUrl behavior (since it gets defaulted in windowStore.js) from:
- main.js
- window.js
- tabs.js

Misc
- pulled out setting values into an enum
- position moved to below "Brave starts with" (in preferences.js)
- resolved circular dependency issue in appUrlUtil
- adding missing "base" element to searchProviders that had it missing (mdn, github, startpage, etc)
- made a newtab option called BLANK and renamed value TEMP. We can change back when ready to go live

Auditors: @kingscott @cezaraugusto
bsclifton added a commit that referenced this issue Nov 1, 2016
Fixes #2106

Updated defaultUrl logic
- windowStore.js now uses new defaultUrl method (from appUrlUtil) instead of config.defaultUrl
- default unknown values to about:blank

Removed conflicting defaultUrl behavior (since it gets defaulted in windowStore.js) from:
- main.js
- window.js
- tabs.js

Misc
- pulled out setting values into an enum
- position moved to below "Brave starts with" (in preferences.js)
- resolved circular dependency issue in appUrlUtil
- adding missing "base" element to searchProviders that had it missing (mdn, github, startpage, etc)
- made a newtab option called BLANK and renamed value TEMP. We can change back when ready to go live

Auditors: @kingscott @cezaraugusto
@bsclifton bsclifton added this to the 0.12.8dev milestone Nov 1, 2016
@srirambv srirambv modified the milestones: 0.12.9dev, 0.12.8dev Nov 3, 2016
@0xMF
Copy link

0xMF commented Nov 16, 2016

Please bring back the empty New Tab option (applies to v. 0.12.9; win32; x64).

@luixxiul
Copy link
Contributor

#5652 addressed the issue but I would have to say I preferred the option than leaving the home page URL empty.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.