Skip to content
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

Changed wording of error page #254

Merged
merged 1 commit into from
Sep 9, 2016

Conversation

razzeee
Copy link
Contributor

@razzeee razzeee commented Aug 18, 2016

  • Redid wording of error page
  • Also redid the order of the items and did a little organization.

Just an idea how it could look, some graphics would also be nice. So please let's get some feedback, as I'm not really an ui guy.

image

@razzeee razzeee force-pushed the improve-error-wording branch from 3edf879 to 33b673f Compare August 18, 2016 18:52
@yuya-oc
Copy link
Contributor

yuya-oc commented Aug 19, 2016

Looks better. "What does the user need to check?" would be more helpful than error details.

FYI, I found a issue that <a> link doesn't perform. But it seems the issue is not related to this PR.

@razzeee
Copy link
Contributor Author

razzeee commented Aug 19, 2016

Sorry, ment to say that about the link, but somehow forgot. :)

@jasonblais
Copy link
Contributor

Looks much better, thanks @razzeee for your work here!

Propose queuing the proposal in UX Design channel where the Mattermost team can offer their feedback.

@razzeee
Copy link
Contributor Author

razzeee commented Aug 24, 2016

This is what the ux team came up with. As I'm on war with CSS I'm pretty sure I will fail at centering everything, but let's see.
screen

@razzeee razzeee force-pushed the improve-error-wording branch 2 times, most recently from a4963e9 to 8305d61 Compare August 24, 2016 21:29
@razzeee
Copy link
Contributor Author

razzeee commented Aug 24, 2016

image
So here's a first version with some things still off.
I especially don't like that we don't let the user know that we're refreshing periodically.

@jasonblais
Copy link
Contributor

Really nice work here, thanks @razzeee!

I'll check with the platform team if they have time to help out with CSS. @asaadmahmood is fantastic with it, so he might be able to do tweaks pretty quickly.

@razzeee razzeee force-pushed the improve-error-wording branch from 8305d61 to 2475671 Compare September 3, 2016 09:25
@razzeee
Copy link
Contributor Author

razzeee commented Sep 3, 2016

@asaadmahmood did some look and feel changes, so we're now at this:

image

@jasonblais jasonblais added this to the v1.4.0 milestone Sep 4, 2016
@jasonblais
Copy link
Contributor

Looks great to me. Big thanks @razzeee and @asaadmahmood!

We're really improving the UX standard with v1.4, which is awesome.

@yuya-oc: @asaadmahmood worked on this on his Mac, and this works on Windows. Do you think further testing is needed?

<hr />
<p>We're having trouble connecting to Mattermost. If refreshing this page (Ctrl+R or Command+R) does not work please verify that:</p>
<br />
<p>
Copy link
Contributor

Choose a reason for hiding this comment

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

The console shows index.js:1812 Warning: validateDOMNesting(...): <ul> cannot appear as a descendant of <p>. In my setting, which has three teams and the third is incorrect URL, I could not click the second tab while showing the third tab. Is this related?

@yuya-oc
Copy link
Contributor

yuya-oc commented Sep 5, 2016

The styling looks fine. Probably this is not related to OS excepting fonts, so I think we need just one tester for next testing.

@razzeee razzeee force-pushed the improve-error-wording branch 2 times, most recently from c53df34 to 56cdecf Compare September 5, 2016 22:44
<ListGroupItem>Is the server alive?</ListGroupItem>
<ListGroupItem>Is the URL correct?</ListGroupItem>
</ListGroup>
<div style={ errorPage.tableStyle }>
Copy link
Contributor

Choose a reason for hiding this comment

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

By removing these two <div>, tabs properly works while showing the error page. So you might need to adjust the vertical position with other ways.

@razzeee razzeee force-pushed the improve-error-wording branch from 56cdecf to c8dd114 Compare September 7, 2016 19:38
@razzeee
Copy link
Contributor Author

razzeee commented Sep 7, 2016

Should be fixed now

@razzeee razzeee force-pushed the improve-error-wording branch from c8dd114 to b294a44 Compare September 7, 2016 20:16
@yuya-oc
Copy link
Contributor

yuya-oc commented Sep 9, 2016

The tabs work properly on Windows 10 and OS X.

@razzeee Just curious, what was the point in the last push?

@razzeee
Copy link
Contributor Author

razzeee commented Sep 9, 2016

@yuya-oc
This line b294a44#diff-46044d7460b0a55fc983668900dbd4cbR475
was set to -70 in the code @asaadmahmood delivered. Setting it to 0 fixed it. It might not be 100% in the vertical mid now.

@yuya-oc
Copy link
Contributor

yuya-oc commented Sep 9, 2016

I see. Thanks!

@yuya-oc yuya-oc merged commit 52f451e into mattermost:master Sep 9, 2016
@razzeee razzeee deleted the improve-error-wording branch September 9, 2016 15:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants