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

restyle preferences payments #6101

Merged
merged 2 commits into from
Jan 11, 2017
Merged

restyle preferences payments #6101

merged 2 commits into from
Jan 11, 2017

Conversation

jkup
Copy link
Contributor

@jkup jkup commented Dec 8, 2016

  • Submitted a ticket for my issue if one did not already exist.
  • Used Github auto-closing keywords in the commit message.
  • Added/updated tests for this change (for new code or code which already has tests).
  • Ran git rebase -i to squash commits (if needed).

Fix #5494

Auditors @bsclifton @bradleyrichter

Here is a screenshot of this branch:
screen shot 2016-12-08 at 2 20 43 pm

Spec image:
screenshot 2016-12-17 17 31 04

@jkup jkup added design A design change, especially one which needs input from the design team. QA/test-plan-specified labels Dec 8, 2016
@jkup jkup added this to the 0.13.1 milestone Dec 8, 2016
@jkup
Copy link
Contributor Author

jkup commented Dec 9, 2016

@bsclifton there is a seemingly related test failing on this build but it appears to be failing on master too

  1. synopsis can disable site:
    Error: Promise was rejected with the following reason: TypeError: Cannot read property 'ledgerPayments' of undefined

Is this a known failure?

@bsclifton
Copy link
Member

bsclifton commented Dec 9, 2016

Just checked it out...

  • The verified icon doesn't show properly
    screen shot 2016-12-09 at 12 13 56 am

  • Clicking remove does kill the entry. I can then go to shields and undo the removal... but the data appears to be lost for that. Is this intentional? I know this PR is doing the same thing as when you right click and pick "Do not show this entry". Maybe @mrose17 or @bradleyrichter can confirm this is correct

  • The table looks great! 😄 love seeing it match the others

  • The removal of the 60% style on sortableTable breaks the history page. It may have been sloppy of me to introduce that (instead of styling the columns individually). Fixed! 😄

The other sortableTables look OK

  • Preferences > Search
  • Bookmarks manager
  • about:brave

The torrent viewer and torrent file list pages use the sortable tables too, but I'm not familiar with how to pull them up. @alexwykoff, @srirambv, or @luixxiul - can one of you help me with that?


td {
position: relative;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

removing this breaks the position of the verified icon.

@bsclifton
Copy link
Member

@jkup regarding the test- I tried it out... I think the test is written correct; it probably broke though when the default time for a visit was bumped up. We can likely increase that timeout to fix the issue. Since it's failing on master, I made an issue to track it:
#6110

@jkup
Copy link
Contributor Author

jkup commented Dec 13, 2016

@bsclifton is this one ready to merge?

@bsclifton
Copy link
Member

@jkup yup! looks good to me 😄

@luixxiul
Copy link
Contributor

Was the position of verified icon confirmed?

@bsclifton
Copy link
Member

@luixxiul thanks for the reminder! No- it still does not look correct

@jkup can you fix it up please? 😄
screen shot 2016-12-14 at 10 12 05 am

@jkup
Copy link
Contributor Author

jkup commented Dec 14, 2016

@luixxiul @bsclifton doh! thanks for reminding me! It actually looks like we can add position:relative to all sortableTable td's and they all look great! Updated the commit.

@bsclifton
Copy link
Member

@jkup can you rebase? thanks 😄

@jkup
Copy link
Contributor Author

jkup commented Dec 15, 2016

Done. I ran into a lot of merge conflicts but I checked all our sortable tables and they appear to look right!

margin: 10px 75px;
}

.modal .dialog.paymentHistory .sectionTitle {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you can remove this.

text-align: left;
}

#paymentHistory {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ditto.

@jkup
Copy link
Contributor Author

jkup commented Dec 16, 2016

Thanks @luixxiul! Updated.

@luixxiul
Copy link
Contributor

This change causes some regressions on about:preferences#payments. I will make it more specific, adding notes in preferences.less

@jkup
Copy link
Contributor Author

jkup commented Dec 17, 2016

Yeah I had put this PR up before you made all those design tweaks to prefs#payments. If you could let me know anything specific that would be great and I'll take care of it.

@luixxiul
Copy link
Contributor

@jkup thanks, I'll add a commit soon. Please don't squash it and let @bsclifton review it ;-)

@bsclifton
Copy link
Member

@luixxiul there is a CSS/LESS conflict here; can you please resolve this (either in GitHub's UI or by checking out / rebasing via command line). Thanks 😄

@luixxiul
Copy link
Contributor

luixxiul commented Jan 10, 2017

Otherwise I'm wondering if this PR should be closed as I think this has been superseded with #6422, where those two commits were cherry-picked. Also the PR includes fixes which are not added to this PR.

wdyt @jkup @bsclifton ?

@luixxiul luixxiul added needs-info Another team member needs information from the PR/issue opener. and removed PR/ready-for-merge labels Jan 10, 2017
@bsclifton
Copy link
Member

bsclifton commented Jan 10, 2017

@luixxiul let's keep 'em separate for now. When it's "go time", we'll want to merge this one first. Each subsequent PR will then require a rebase anyways, where we can remove the cherry picked commits

@bsclifton bsclifton added PR/ready-for-merge and removed needs-info Another team member needs information from the PR/issue opener. labels Jan 10, 2017
@luixxiul
Copy link
Contributor

Ah right, we can remove the cherry-picked commits and I've totally forgotten about that! :D

@bsclifton
Copy link
Member

bsclifton commented Jan 10, 2017

This one is failing tests: cc: @jkup
npm run test -- --grep="synopsis can disable site"

I think it's looking in the wrong place. Here's a dump of the appState:
https://gist.github.com/bsclifton/4ec2c3bf55b13ef4ac8cf4564dcf8380

fix #2957
note that this partially un-fixes #1928.

Auditors: @alexwykoff

Test Plan:
1. go to developer.apple.com
2. click on 'Account' in the top right
3. enter your apple username and password
4. the login page should redirect to https://developer.apple.com/
5. after the redirect, you should still see a password manager dialog from Brave that says 'Would you like Brave to remember the password for [username] on https://idmsa.apple.com?'
@jkup
Copy link
Contributor Author

jkup commented Jan 11, 2017

@bsclifton test is fixed!

@luixxiul let's try not to add commits to existing PRs. Should your CSS commit be rebased into mine? If so, can you rebase the now 3 commits into one? If not, maybe pull yours out into a separate ticket so I can rebase my two?

@luixxiul
Copy link
Contributor

luixxiul commented Jan 11, 2017

@jkup: please drop my 886cf71 of this PR, as it was cherry-picked in #6422 and I asked @cezaraugusto to use it. / cc: @cezaraugusto

@bsclifton bsclifton changed the base branch from master to 0.13.1-branch January 11, 2017 06:41
@bsclifton
Copy link
Member

Last travis-ci run shows 2 unrelated about:bookmark errors; I re-ran those locally and it's working as expected 😄 Merging...

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
design A design change, especially one which needs input from the design team. feature/rewards l10n QA/checked-macOS QA/checked-Win32 QA/checked-Win64
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants