-
Notifications
You must be signed in to change notification settings - Fork 99
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
No Thumbnail with SVG image #703
Comments
Hi @corbym, |
I can write a test without all the plantuml generation stuff - it should run with vanilla jgiven dependencies, is this acceptable?
|
Some things I have noticed:
|
From @andru47 who took a look into the issue: |
Hi @corbym so we found out that JGiven does not consider SVG a binary file (because it isn't one) and consequently does not produce a thumbnail for it. A separte problem is that the HTML display app seems to not handle SVG in the same manner as image attachments either. They should be displayed, but will lack some convenince features. The HTML app unfortunately requires more analysis. |
Some more thoughts:
|
@andru47 please have a look at Matt's suggestions |
Hi @corbym, With that in mind, the next step would be to modify and publish the npm html app to fix how svg files are handled. We will keep you updated and we will also take into the account the feedback for general attachments. |
Hi again, |
I am trying to add an SVG image to a jgiven report as an attachment:
However, there are a number of problems:
The image has no thumbnail version (and so looks strange in the report). Clicking the link renders the image correctly in the browser.
inlining it does so correctly but renders it unable to function correctly (the image has hover overs and links in it). You cannot click the image to open it in the browser, however.
MediaType.imageUtf8("svg+xml; charset=utf-8")
dance for jgiven to render it at all.. it gets the incorrect file extension when it's mediatype is assessed by the report generation step.What is the correct way to do this? Please help.
The text was updated successfully, but these errors were encountered: