You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use graphviz in my Sphinx documentation and would like to reuse links automatically generated by the RestructuredText code.
The output I get from
Hello
-----
Test of a graph
.. graphviz::
digraph process {
a [label="first", href="http://google.com"];
b [label="second", href="#World"];
a -> b;
}
World
-----
Something else.
is correct, but despite the fact that the generated image is an SVG, firstand second are not clickable:
If I right click the embedded image and open it in a new tab, it has active links I can click on. It looks like if embedding the image prevented the links from being active.
Hello @tk0miya and @wsw70,
Found this issue while looking for a way to make the PNG images generated from the graphviz extension clickable.
Is there a way to open the PNG in another window with a click?
Hello @Ellon , I recommend you to ask in the https://groups.google.com/g/sphinx-users mailing list, Stack Overflow, or open a new feature request if you are certain that what you're asking cannot be done at the moment. Commenting on a 6 year old issue that's unrelated to your question makes it less visible and you're less likely to get help.
question initially asked at stackoverflow but it looks like this is rather a bug
I use graphviz in my Sphinx documentation and would like to reuse links automatically generated by the RestructuredText code.
The output I get from
is correct, but despite the fact that the generated image is an
SVG
,first
andsecond
are not clickable:If I right click the embedded image and open it in a new tab, it has active links I can click on. It looks like if embedding the image prevented the links from being active.
The elements of my
conf.py
relevant to graphviz:Is there something specific to set up in Sphinx to have this behaviour for embedded graphs?
The text was updated successfully, but these errors were encountered: