-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Editor: Mobile editor redesign (phase 2) #4686
Editor: Mobile editor redesign (phase 2) #4686
Conversation
I had a quick look as is and I'm seeing a console error: |
@@ -73,7 +81,10 @@ export default React.createClass( { | |||
aria-label={ this.translate( 'Show advanced status details' ) } | |||
aria-pressed={ !! this.props.advancedStatus } | |||
> | |||
<Gridicon icon="cog" size={ 16 } /> | |||
{ this.props.advancedStatus | |||
? <Gridicon icon="chevron-up" size={ 18 } /> |
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.
This is a regression, should be cog icon.
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.
It's an downward / upward arrow in the redesign mock-ups. @folletto was this an intended change, or just a copy&paste error or something?
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 design was done before that change went in production. So it's misaligned, and it should be a cog. Sorry about that.
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.
No problem, that's what happens when stuff changes, fixed :)
@DanReyLop hey, do you mind including a screenshot on the description showing where this is at for easy reference? |
@@ -343,11 +323,26 @@ const PostEditor = React.createClass( { | |||
site={ site } | |||
type={ this.props.type } | |||
/> | |||
<div className="editor__site"> |
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.
This class would be a bit misleading given that it also includes the status. I'd look for a better name.
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 main component in that bar is the site, the status is like an small add-on. Also, I'm trying to rationalize my decision because I can't come up with a better name, if you do I'll search&replace it :)
I think we should only have one notice and change focus to content. Alternatively, we may want to switch to global-notices for this. |
@folletto Thanks for the screenshots. @alisterscott I'm not having that console error. Did you try running @mtias I think presenting the notice in the tab where the user is would be less confusing. About the other comments, I'll wait to fix them until we decide if we change the approach to this redesign. |
All good now thanks! I ran |
4c73528
to
19ab894
Compare
390b54b
to
bdf6ed2
Compare
I left a few comments trying to solve some of the questions. I hope that's enough. :) Once these are sorted, would be possible to have a list of what's still pending (if anything) in order to get this merged? This is a big change so I feel would be useful to have a "We're here" overview. :) |
Well, if you agree with the latest changes, there should be nothing pending. I would need to:
|
19ab894
to
ea7ba8d
Compare
ad42159
to
0973d8e
Compare
I've updated this PR and #4456 with As I said, this PR and #4456 have a different set of commits to make them easier to review, but they need to be deployed at the same time (or better yet, just deploy this one and close the other). The tip of this branch has all the code of the mobile editor redesign, so if you're testing locally, it's enough to test this branch. |
You can test this live on real devices using: https://calypso.live/?branch=update/4266-mobile-editor-redesign-2 |
I've tested this today:
Featured Image Over Site Title Featured Image that was edited above editor Cursor on actions screen Switching back to edit screen when cursor shown Desktop back/drafts loses spacing when expanding side areas |
Editor: Enable alt text editing for existing images (feature flagged)
…ishButton component
…ly on layoutFocus instead
…c) to the metadata tab in mobile screens
… of the mobile editor
…itor view and it appears in the metadata view
0973d8e
to
d013221
Compare
Looks like it's not possible to change the target branch of a PR after it's created. I've created a new PR with the @alisterscott comments fixed: #5987 |
This PR includes the following changes on the mobile editor:
Notice
bar appear on both tabs, and make it disappear when the user changes the tabNote that this PR follows #4456. The code on this branch (
update/4266-mobile-editor-redesign-2
) is the complete redesign, but the diff betweenupdate/4266-mobile-editor-redesign-2
andupdate/4266-mobile-editor-redesign
is only the changes I've listed above. Please tell me if there is a less confusing approach to managing this :)cc / @aduth @alisterscott @folletto