-
Notifications
You must be signed in to change notification settings - Fork 909
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Brave Today: dismiss intro card if it has been viewed for 4 seconds #7111
Conversation
) | ||
// don't render if user prefers an empty page | ||
if (props.newTabData.showEmptyPage && !props.newTabData.isIncognito) { | ||
return <div /> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: any reason not to just return null
here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not sure, I just moved this code from a class to a function (for no particular reason in the end as I didn't use). I think the div is for the blank page? But there's no styling. And in fact this pref is not real. So this code will never fire! We should probably remove that at some point then...
Seems like CI is ok, ping @bsclifton @ryanml |
@petemill just needs rebase - but I can check out after that 😄 |
a68b6c8
to
61d58d6
Compare
Intro Card (and the current tab) has to be fully in view
61d58d6
to
098e065
Compare
rebased |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
changes lgtm
Linux had unrelated test failure |
Stores a profile pref when the Intro Card (and it's Tab) have been in view for 4 seconds. Does not immediately get removed from page, it just won't show up on the next page load.
Resolves brave/brave-browser#12960
Submitter Checklist:
npm run lint
,npm run gn_check
)git rebase master
(if needed).git rebase -i
to squash commits (if needed).QA/Yes
orQA/No
) to the associated issuerelease-notes/include
orrelease-notes/exclude
) to the associated issueTest Plan:
On issue
Reviewer Checklist:
After-merge Checklist:
changes has landed on.