-
Bug
-
Resolution: Duplicate
-
Minor
-
None
Hello 👋
Here comes a funny UI bug:
First, it is browser dependant. I cannot reproduce it on FireFox, but can reproduce on Chromium based browsers.
In a MultiBranch pipeline, under certain circumstances, the job's name can crawl away from the mouse pointer, making it impossible to click it.
Note that this bug totally depends on the browser's width. If you reduce it enough to have a "card layout" for mobile, the bug cannot be reproduced anymore.
And if you go full screen on a wide monitor, the bug cannot be reproduced again.
If you zoom out, the bug doesn't appear either, which is a workaround for that bug.
And basically, there is a correlation between the browser's width and the length of the job name allowing to trigger the bug. The smaller the width, the smaller the required job name.
While investigating, I found out that it is probably due to that small menu added on the right side of the job's name when hovering:
Which comes from using the `model-link` CSS class.
Going further in the analysis, I saw in the table that other elements had such links, but were not impacted by the bug, such as elements from the Last Success column.
Having a look at more details, it looks like these elements have the following CSS classes for the a elements: jenkins-table_link jenkins-table_badge model-link inside. OTOH, the a elements in the name column only have the model-link inside classes.
Using the Developer Tools in the browser, if you add the missing classes in the Name column, the bug cannot be triggered anymore.
I have used
```
org.kohsuke.stapler.jelly.JellyFacet.TRACE=trueorg.kohsuke.stapler.jelly.ReallyStaticTagLibrary.EMIT_LOCATION=true
```
to identify the possible source of this, and it led me to:
which indeed seems to be missing those classes.{{}}
- duplicates
-
JENKINS-72026 UI: Branch names dance down the screen (unclickable) in multi-branch pipeline jobs
-
- Closed
-
Thanks for reporting the issue! Has not been investigated yet for a root cause and a resolution, but was reported in
JENKINS-72026. I'm resolving this as a duplicate. Would love to have someone do the bisect to identify the root cause of the change of behavior.