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
Bug 1880410: convert pipeline visualization node to SVG #6676
Conversation
@rottencandy: This pull request references Bugzilla bug 1880410, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@rottencandy: This pull request references Bugzilla bug 1880410, which is valid. 3 validation(s) were run on this bug
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/hold |
/bugzilla refresh |
@rottencandy: This pull request references Bugzilla bug 1880410, which is valid. 3 validation(s) were run on this bug
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@rottencandy: This pull request references Bugzilla bug 1880410, which is valid. 3 validation(s) were run on this bug
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/hold cancel |
/kind bug |
/retest |
Code change looks valid, but I find some UI difference.
|
Thanks for the review @jerolimov !
Updated the max length. I think there will be some differences here. The old version used a CSS solution(using
I tried to replicate the old version which also had hover shadow, albeit was very subtle. I can add the non-hover shadow as well if you think it's better.
Updated.
Thank you for catching this, I seem to have missed it. Updated.
Not sure why it appears bigger, I've set it to the smallest possible width of EDIT: |
Also about the bottom border, I think there is a bit of inconsistency between browsers. Should I follow the Firefox appearance, or the Chromium one? |
1748565
to
61c05ae
Compare
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.
return ( | ||
<SyncAltIcon | ||
{...props} | ||
className={cx('fa-spin', { 'pipeline-status-icon__spin': shiftOrigin })} |
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.
className={cx('fa-spin', { 'pipeline-status-icon__spin': shiftOrigin })} | |
className={cx('fa-spin', { 'pipeline-status-icon--spin': shiftOrigin })} |
BEM is
- Block (
pipeline-status-icon
) - Element (
pipeline-status-icon__someWrapper
) -- kinda like a sub Block - Modifier (
pipeline-status-icon--spin
) -- when you want it to be "modified" based on a prop
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.
Updated.
/hold cancel |
FWIW, frontend test failure is lack of |
Replacing the |
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.
Tiny nit, will test it out once I finish compiling 🙂
} | ||
&__trigger-underline { | ||
fill: var(--pf-global--Color--100); | ||
&__hover { |
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.
&__hover { | |
&--hover { |
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.
Updated.
Please one of you toss a review on this as well. If I don't see any review by EOD tomorrow, I'll LGTM it. |
/retest |
Verified locally, works fine. Thanks @rottencandy |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: andrewballantyne, jerolimov, karthikjeeyar, rottencandy The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@rottencandy: The following test failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
/retest Please review the full test history for this PR and help us cut down flakes. |
1 similar comment
/retest Please review the full test history for this PR and help us cut down flakes. |
@rottencandy: All pull requests linked via external trackers have merged: Bugzilla bug 1880410 has been moved to the MODIFIED state. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Fixes:
https://issues.redhat.com/browse/ODC-3661
Analysis / Root cause:
There are several rendering issues with the Pipeline Visualization Nodes (aka Tasks). This needs to be handled better and the whole thing is currently rendered through a foriegnObject inside the SVG visualization.
Solution Description:
Convert pipeline visualization node to SVG.
Screen shots / Gifs for design review:
(Should ideally be unchanged)
Unit test coverage report:
Unchanged.
Browser conformance: