-
Notifications
You must be signed in to change notification settings - Fork 687
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
Ui fixes #1538
Ui fixes #1538
Conversation
64f0871
to
61f7365
Compare
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.
Solid changes @heartsucker 👍 . I've added a couple of comments inline. Once addressed this is good to merge in.
securedrop/sass/_base.sass
Outdated
font-size: 30px | ||
color: #004080 |
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.
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.
Actually the bigger problem is that most places we use h2
, we should be using h1
, and the only places we use h1
, should definitely be h2
. Ha. I'll make some more changes.
@@ -34,15 +34,16 @@ | |||
</h2> | |||
<hr class="cut-out" /> | |||
<p>If this is your first time submitting documents to journalists, start here.</p> | |||
<a href="/generate" class="btn alt block" id="submit-documents-button"><img id="warning-close" src="{{ url_for('static', filename='i/font-awesome/white/cloud-upload.svg') }}" width="17px" height="17px"> Submit Documents</a> | |||
{# adding a break between 'submit' and 'documents' to make both containers equal sized #} | |||
<a href="/generate" class="sd-button btn alt block" id="submit-documents-button">SUBMIT<br/>DOCUMENTS</a> |
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.
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.
I'm not seeing it display like this. What OS are you testing this on? I'm on Firefox 51.0.1 / Debian Stretch. Also, how are you getting TB to reach localhost?
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.
Check out this link for how to allow TB to reach localhost. I was running Tor Browser 6.5 on Mac OS X when I made that screenshot. Check it out in Tor Browser (it's based on Firefox 45.7.0 so the CSS might render differently) and let me know if you can't reproduce what I see above
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.
The "no proxy" option isn't working for me. Also TB 6.5. Hmm. If you want to branch this and make a tweak, go ahead.
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.
Sure, I'll take a look
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.
Ok branched off this and in fix-box-sizes-on-src-interface-index
there is a single commit 74f612b fixing these boxes to be the same size. Now in Tor Browser this looks like:
I'll submit a PR against this repo to get that commit merged in after I merge your PR in
securedrop/sass/journalist.sass
Outdated
|
||
&:hover | ||
color: #999 | ||
background-color: white |
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.
Verified this fixes the CSS on the journalist interface 👍
Hey @heartsucker - thanks for addressing these comments - everything looks good on my end now. If you fix the functional test failure I will merge this in 😄 |
@redshiftzero Sounds good. It might take a few days for me to get to it. New job 'n all. |
fixes item 1 from issue 1536
fixes item 4 in issue 1536
fixes item 5 in 1536
rebasing of sass changes left out this bit of css
|
Hey @heartsucker—my bad on that hex call, sorry abt that! I got sloppy, it should visually match the primary button—yes, yes. :) I updated my spec to cite #727c9b as the recco'd stroke color (it's a taaaad darker than the button blue). Thx for catching & asking! |
Ok, I created #1552 as a go-to place to solidly document global basic things between all three UIs: Journalist, Source, and Admin. I had used |
D'oh. Note to self: don't debug on the S-bahn. :( |
@redshiftzero Should be good to merge now. |
@heartsucker I took another look at this - looking much better - just a couple more small things 🙏 : There was a rebase snafu on
Finally, the index looks like this in Tor Browser:
Also thanks @ninavizz for that quick response 💎 |
Are Sources now being asked to enter their passphrase 2x? :( Cancel (or secondary) button should always be visually paired w/ the primary button—no more than ~4px space, between them. Once I'm fully competent with this Terminal/dev-build stuff (that @fowlslegs was extra-awesome spending THREE hours walking me through, on Tuesday!) that's still super brain-hurts-new to me, I'll do all I can to comment directly on the code itself. Longer-term, a UI library of common elements—such as button pairs!—with "how to modify w/o breaking code or visual standards" notes will be a nice thing to create, so all these repeat-elements can be way easier to wham-bam cut-and-paste/modify. More time spent building + designing, less time spent replicating the saaaame things over and over again. The Y!UI library was built when I was at Yahoo!, and maan, that thing was awesome! |
No, this was just a messy rebase I didn't check carefully enough. I only
checked the things I fought changed and not everything. Some of the changes
broke the design and some are just functionally wrong (double password).
Changes soon (hopefully).
Am 03.02.2017 22:22 schrieb "Nina Eleanor Alter" <[email protected]>:
… Are Sources now being asked to enter their passphrase 2x? :(
Cancel (or secondary) button should always be visually paired w/ the
primary button—no more than ~4px space, between them. Once I'm fully
competent with this Terminal/dev-build stuff (that @fowlslegs
<https://github.com/fowlslegs> was extra-awesome spending THREE hours
walking me through, on Tuesday!) that's still super brain-hurts-new to me,
I'll do all I can to comment directly on the code itself.
Longer-term, a UI library of common elements—such as button pairs!—with
"how to modify w/o breaking code or visual standards" notes will be a nice
thing to create, so all these repeat-elements can be way easier to wham-bam
cut-and-paste/modify. More time spent building + designing, less time spent
replicating the saaaame things over and over again. The Y!UI library was
built when I was at Yahoo!, and maan, that thing was awesome!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1538 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AD0DALzc0pd5YVPG81KgF_FJ838cQblDks5rY5qzgaJpZM4Lw0ux>
.
|
Cool! I (and lots of others in the UX-for-security community) just find that whole "Enter your password in a second time!" pattern-standard to be absurdly asinine... and wanted to make sure it wasn't sought, here. I should trust my experience with you thus far, that you're not an advocate for piffy security-theatrics... :D |
@redshiftzero Apologies for the sloppy rebase and time wasted. This one should do it, though. However, two notes about things that look less than ideal. Not sure if these should be tackled here or in another issue.
@ninavizz Comments / suggestions? |
26d527d
to
8729ece
Compare
@heartsucker no worries. Thanks for making these changes! I've checked this out and it now looks great - I'm going to merge this in now given that the changes are solid and we've already had a long back and forth in this PR. But! If you want to make another followup PR you could make the following changes to address these (IMHO valid but much smaller) concerns:
|
@redshiftzero You got it. :D |
Makes some of the suggested changes in #1536 and fixes an incomplete rebase from #1349.