Conversation
5aadf13 to
1241d04
Compare
039d232 to
5e2f69a
Compare
| await act(async () => { | ||
| jest.advanceTimersByTime(500); | ||
| }); | ||
|
|
There was a problem hiding this comment.
wondering why the assertion on signature modal was removed, and we need to manually handle the timers here?
There was a problem hiding this comment.
the assertion was to check whether or not it's visible, but we're mount/unmounting for modal v2
modal v2 has a transition animation with 300ms, so that's just to skip the animation
There was a problem hiding this comment.
why is it not needed for the other tests?
5e2f69a to
a6832f9
Compare
31d0194 to
dae2cc2
Compare
| max-height: none; | ||
| margin: 0 auto; | ||
| padding: ${Spacing["spacing-16"]}; | ||
| box-shadow: ${Shadow["lg-strong"]}; |
There was a problem hiding this comment.
what does the box shadow do?
There was a problem hiding this comment.
Modal.Box had this styling before but ModalV2.Card has xs-strong. Just making sure the styling is similar as the old one as much as possbile
There was a problem hiding this comment.
checking Figma, it is indeed meant to be shadow lg-strong. will create a separate ticket to align ModalV2
| width: 100%; | ||
| margin: auto; | ||
| padding: ${Spacing["layout-xxl"]} ${Spacing["layout-sm"]}; | ||
| export const modalHeader = css` |
There was a problem hiding this comment.
ideally with the new ModalV2.Header we no longer need to specify so many custom styles. what are the changes here and why are they needed?
There was a problem hiding this comment.
this was because the header fonts and spacing somehow after changing to using ModalV2 is way different to what we were using when it's still Modal
…ard on mobile specific styling
…hanges to accomodate different scenarios
…dding test case for custom header
9746527 to
c087d82
Compare
| ${MediaQuery.MaxWidth.sm} { | ||
| &[data-mobile-landscape] { |
There was a problem hiding this comment.
are the selectors supposed to be nested? this means the screen width is sm AND the screen height is sm
in the previous selectors, they were comma separated which should have a OR logic
| * `closeButtonPosition`. Omit for a close-button-only header. | ||
| */ | ||
| title?: string | undefined; | ||
| title?: React.ReactNode | undefined; |
There was a problem hiding this comment.
Figma shows a standard heading xs now so the customisation is not needed
qroll
left a comment
There was a problem hiding this comment.
still somewhat confused as to why some new styles are needed
testing against the latest master, I'm able to strip down most of the styles https://github.com/LifeSG/react-design-system/tree/RL/CCUBE-2221, with the main discrepancy being the header spacing
Type of changes
Description of changes
Checklist