Visual bug in on-hover behavior for parent/child pipelines
### Summary Something I noticed today when trying to take a screenshot for the docs: When you hover on the child pipelines, it highlights the job that triggered the pipeline, but for some reason the job shape is changing to a rectangle: - ![child-pipeline-bug](/uploads/5e3a9b5f141479e3ec7b5ddc716ab7a7/child-pipeline-bug.gif) I *thought* this worked when it was implemented, but I have not tested it in a long time. @mgandres pointed out the last time this code was touched might have been in (not thoroughly researched yet): https://gitlab.com/gitlab-org/gitlab/-/merge_requests/60039 ### Example pipeline See: https://gitlab.com/marcel.amirault/test-project/-/pipelines/369552522 ### Relevant logs and/or screenshots <!-- Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's tough to read otherwise. --> ### Output of checks <!-- If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com --> #### Results of GitLab environment info <!-- Input any relevant GitLab environment information if needed. --> <details> <summary>Expand for output related to GitLab environment info</summary> <pre> (For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:env:info`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`) </pre> </details> #### Results of GitLab application Check <!-- Input any relevant GitLab application check information if needed. --> <details> <summary>Expand for output related to the GitLab application check</summary> <pre> (For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:check SANITIZE=true`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true`) (we will only investigate if the tests are passing) </pre> </details> ### Possible fixes <!-- If you can, link to the line of code that might be responsible for the problem. -->
issue