During a test migration, I have a pipeline of 10 stages. The displayed width of the pipeline exceeds the width of my display/browser. That is ok, but in this case, the pipeline graphic itself offers scrollbars to navigate and the graphic is cut at the right. It is a bit cumbersome to navigate down in the browser to find the scrollbar of the embedded pipeline and use that, thus using both scrollbars, first the one of the browser, then the one of the pipeline graphic. It would be better to have a solution completely based on the browser e.g. that the pipeline itself is fully displayed (but some content is hidden on the right if the width is too big) and the browser automatically detects that more content is available and currently hidden, and adds its scrollbars. In short words: the scrolling should be based entirely on the browser, such as with other Jenkins components.