-
Notifications
You must be signed in to change notification settings - Fork 938
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
Layout changes to listing and tx (enquiry) page #988
Conversation
lyyder
commented
Dec 27, 2018
- 3 baselines between the listing title and the Price per night on TX page (enquiry), it was 4.
- 8 baselines between the Price per night and the “Start date”, it was 10.
- 8 baselines between the Date’s line and the Booking breakdown, it was 9.
Apply design baseline definitions on BookingDatesForm, BookingPanel and ListingPage.
@@ -89,6 +90,7 @@ const BookingPanel = props => { | |||
: 'BookingPanel.perUnit'; | |||
|
|||
const classes = classNames(rootClassName || css.root, className); | |||
const titleClasses = classNames(css.bookingTitle, titleClassName); |
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 just creates a string
<h2 class="BookingPanel__bookingTitle_asdfasd TransactionPanel__bookingTitle_werwee">
Which means that both styles come from main.bundle.css and the import order might change the overriding rules.
maybe change this toclassNames(titleClassName || css.bookingTitle)
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.
Plus override all the style rules.
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.
Just one comment.
Fix the title class overriding so that the css load order does not affext the styles. Also removes a redundant media query definition.