fix: Embed booker top margin embed#10357
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
3 Ignored Deployments
|
|
Thank you for following the naming conventions! 🙏 |
5af1386 to
4bdf9f1
Compare
| isEmbed && layout === BookerLayouts.MONTH_VIEW && "border-booker sm:border-booker-width", | ||
| !isEmbed && layout === BookerLayouts.MONTH_VIEW && "border-subtle", | ||
| // We don't want any margins for Embed. Any margin needed should be added by Embed user. | ||
| layout === BookerLayouts.MONTH_VIEW && isEmbed && "mt-0" |
There was a problem hiding this comment.
Removing the margin in the correct way now. It was working accidentally somehow but after an unrelated fix of returning null from the component in a case, it stopped working.
📦 Next.js Bundle Analysis for @calcom/webThis analysis was generated by the Next.js Bundle Analysis action. 🤖 This PR introduced no changes to the JavaScript bundle! 🙌 |
|
🤖 Meticulous spotted visual differences in 32 of 230 screens tested: view and approve differences detected. Last updated for commit eeb97ab. This comment will update as new commits are pushed. |
Current Playwright Test Results Summary✅ 97 Passing - Run may still be in progress, this comment will be updated as current testing workflow or job completes... (Last updated on 07/25/2023 09:52:31am UTC) Run DetailsRunning Workflow PR Update on Github Actions Commit: eeb97ab Started: 07/25/2023 09:50:21am UTC
|
|
|
2 Test Cases Affected |
Test Case Results
| Test Case | Last 7 days Failures | Last 7 days Flakes |
|---|---|---|
|
Popup Tests should be able to reschedule
Retry 2 • Retry 1 • Initial Attempt |
1.22% (2)2 / 164 runsfailed over last 7 days |
98.17% (161)161 / 164 runsflaked over last 7 days |
|
Popup Tests should open embed iframe on click - Configured with light theme
Retry 1 • Initial Attempt |
0% (0)0 / 164 runsfailed over last 7 days |
4.27% (7)7 / 164 runsflaked over last 7 days |
f346c13 to
eeb97ab
Compare
| const mainElBoundingRect = mainElement.getBoundingClientRect(); | ||
| resolve(mainElBoundingRect.top); | ||
| } else { | ||
| setTimeout(tryGettingBoundingRect, 500); |
There was a problem hiding this comment.
With the recent change in Booker, main element isn't SSRd. SSR has null element rendered. It shows on client and thus we need to wait for the element to be available on client now.
What does this PR do?
Type of change
How should this be tested?
Mandatory Tasks
Checklist