-
Notifications
You must be signed in to change notification settings - Fork 361
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
fix: [M3-8929] - Unexpected gradient on Linode Detail with VPC interface #11289
Conversation
<StyledGradientDiv> | ||
<CopyTooltip | ||
copyableText | ||
text={configInterfaceWithVPC.ipv4.vpc} | ||
/> | ||
</StyledGradientDiv> | ||
<StyledCopyTooltip text={configInterfaceWithVPC.ipv4.vpc} /> | ||
{configInterfaceWithVPC.ipv4.vpc} | ||
<Box sx={{ ml: 1, position: 'relative', top: 1 }}> | ||
<StyledCopyTooltip text={configInterfaceWithVPC.ipv4.vpc} /> | ||
</Box> |
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.
For consistency with the other copyable tooltips, we should make both the text and the icon copyable. Technically the gradient too but it's too slight to notice and we should probably remove it in the other places as well. No idea why the gradient broke here and not prior.
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.
For consistency with the other copyable tooltips, we should make both the text and the icon copyable.
This is a good point - agreed.
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.
fixed
No idea why the gradient broke here and not prior.
It is most likely because the gradient is absolutely positioned, and if there is no immediate parent container with a relative
position it will bubble up to to the next relative one, which can be any.
Long story short, there's no need for the gradient on this particular instance
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.
All good now.
Users can technically still click the action menu with the gradient bug, it just requires extreme precision. Thanks for the quick fix, @abailly-akamai!
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.
Thanks @abailly-akamai!
950c22c
to
ff321d5
Compare
Cloud Manager UI test results🔺 1 failing test on test run #4 ↗︎
Details
TroubleshootingUse this command to re-run the failing tests: yarn cy:run -s "cypress/e2e/core/stackscripts/update-stackscripts.spec.ts" |
Cloud Manager E2E Run #6849
Run Properties:
|
Project |
Cloud Manager E2E
|
Branch Review |
develop
|
Run status |
Failed #6849
|
Run duration | 27m 23s |
Commit |
b9442d8749: fix: [M3-8929] - Unexpected gradient on Linode Detail with VPC interface (#11289...
|
Committer | Alban Bailly |
View all properties for this run ↗︎ |
Test results | |
---|---|
Failures |
1
|
Flaky |
1
|
Pending |
2
|
Skipped |
0
|
Passing |
452
|
View all changes introduced in this branch ↗︎ |
Tests for review
cypress/e2e/core/stackscripts/update-stackscripts.spec.ts • 1 failed test
Test | Artifacts | |
---|---|---|
Update stackscripts > updates a StackScript |
Screenshots
Video
|
cypress/e2e/core/linodes/linode-config.spec.ts • 1 flaky test
Test | Artifacts | |
---|---|---|
Linode Config management > Mocked > Creates a new config using non-recommended settings and confirm the informational notices |
Screenshots
Video
|
Description 📝
This PR fixes a wrong implementation of the Linode Detail VPC IP copy UI, introduced by #11172
It is not only a bad visual defect, but also prevents the ability to click on the action menu
Changes 🔄
<StyledGradientDiv>
Preview 📷
How to test 🧪
Prerequisites
Reproduction steps
Verification steps
As an Author, I have considered 🤔
👀 Doing a self review
❔ Our contribution guidelines
🤏 Splitting feature into small PRs
➕ Adding a changeset
🧪 Providing/improving test coverage
🔐 Removing all sensitive information from the code and PR description
🚩 Using a feature flag to protect the release
👣 Providing comprehensive reproduction steps
📑 Providing or updating our documentation
🕛 Scheduling a pair reviewing session
📱 Providing mobile support
♿ Providing accessibility support
I have read and considered all applicable items listed above.
As an Author, before moving this PR from Draft to Open, I confirmed ✅