`link` attribute lacks documentation how it is supposed to be used

[daniel-beck]

Jenkins and plugins versions report

n/a

What Operating System are you using (both controller, and any agents involved in the problem)?

n/a

Reproduction steps

n/a

Expected Results

n/a

Actual Results

n/a

Anything else?

link is a feature unsupported by the current plugin UI (#455). It's only mentioned superficially in the README.

I think SVGs embedded elsewhere as img simply never support onclick in modern browsers, if it ever worked, the risk is simply too great. It was added by @thomas-dee in c13abaa, without usage instructions or pull request, so there is no related discussion. #370 similarly expresses confusion:

That seems to indicate that the "link" parameter is only really useful if you are able to write a script that makes a web request to the icon page and embeds the response content into an HTML document or extracts the target link to create a new hyperlinked image. Such a use case isn't mentioned in the docs though.

That means only standalone access in a separate window is left. I guess it works with an iframe? That seems like a weird, narrow use case TBH.

This feature needs documentation how it is supposed to be used.

Are you interested in contributing a fix?

No response

[daniel-beck]

I guess it works with an iframe? That seems like a weird, narrow use case TBH.

This use case is also being broken by Jenkins 2.539+ potentially setting the frame-ancestors CSP directive. X-Frame-Options in current and older Jenkins releases is only being set for the regular UI, so that would currently work I guess?