-
Notifications
You must be signed in to change notification settings - Fork 198
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
Adjust course theme spacings and alignments #6854
Adjust course theme spacings and alignments #6854
Conversation
This reverts commit 8c7e8e7.
WordPress Dependencies ReportThe
This comment was automatically generated by the |
Codecov Report
@@ Coverage Diff @@
## feature/learning-mode-improvements Automattic/sensei#6854 +/- ##
=====================================================================
Coverage 47.21% 47.21%
Complexity 10131 10131
=====================================================================
Files 499 499
Lines 35886 35886
Branches 283 283
=====================================================================
Hits 16945 16945
Misses 18729 18729
Partials 212 212 Continue to review full report in Codecov by Sentry.
|
@merkushin the following points were fixed.
There is an issue with the spacing on the. I am suspecting it is caused by a " display: flow-root;" that is set here. I still not have sure how it works, but I suspect that removing it will requires to rewrite part of the styles 😢 . |
fixed @Imran92 |
In general it looks really good. I found the only issue with the spacing above the lesson title (or the module name if it exists), it should be 56px (3.5rem). I also found an issue with buttons, but we have a separate card for buttons in progress. |
@merkushin Fixed here 5e45aa9 I just noticed I am seeing different results from you. On your screenshot, the top was 48px, and on my side was 52 (both incorrect but different 🤔 ). Same for the buttons. @Imran92 could you please review it in your env to double-check it? |
I think the difference here is because of the mobile status bar in the design that we don't see in our browser, so we need to "apply" it manually. |
Another thing that I've noticed is #6897 is probably an issue caused by this branch. Should it also be fixed here? |
Nice catch! |
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.
LGTM 👍 We can address the outstanding issue in another PR
Resolves #6834
Proposed Changes
Testing Instructions
npm run start
Extra Notes
There are opportunities to refactor the file using SCSS selector, but to avoid conflicts with other cards, I avoid doing it now.
Pre-Merge Checklist