[Django] #27224: Is possible display SVG by help Django`s view?

11 views

Skip to first unread message

Django

unread,

Sep 14, 2016, 1:31:56 PM9/14/16

to django-...@googlegroups.com

#27224: Is possible display SVG by help Django`s view?
--------------------------------------+--------------------
Reporter: setivolkylany | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Uncategorized | Version: 1.10
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+--------------------
My variable for SVG is next: https://dpaste.de/cPpP

I tried display that code in through view as next

{{{
# my SVG variable
return mark_safe(svg)
}}}

Result:
XML is escaped (mark_safe did not work)

and next

{{{
# my SVG variable
format_html('{}', svg)
}}}

Errors from Chrome`s console:
(index):-1 Uncaught SyntaxError: Invalid or unexpected token
and next

{{{
# my SVG variable
format_html('{}', mark_safe(svg))
}}}

Errors from Chrome`s console:
(index):-1 Uncaught SyntaxError: Invalid or unexpected token

and next

{{{
# my SVG variable
return mark_safe(Template('{{ svg|safe }}').render(Context({'svg': svg})))
}}}

return format_html('{}', svg)
Errors from Chrome`s console:
(index):318 Uncaught SyntaxError: Unexpected token <
pygal-tooltips.min.js:2 Uncaught TypeError: t.addEventListener is not a
function

and next

{{{
# my SVG variable
svg = mark_safe(Template('{{ svg|safe }}').render(Context({'svg': svg})))
return format_html('{}', svg)
}}}

Errors from Chrome`s console:
(index):318 Uncaught SyntaxError: Unexpected token <
pygal-tooltips.min.js:2 Uncaught TypeError: t.addEventListener is not a
function

--
Ticket URL: <https://code.djangoproject.com/ticket/27224>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

Django

unread,

Sep 14, 2016, 1:49:49 PM9/14/16

to django-...@googlegroups.com

#27224: Is possible display SVG by help Django`s view?

Easy pickings: 0 | UI/UX: 0

-------------------------------------+-------------------------------------
Changes (by timgraham):

* status: new => closed
* needs_docs: => 0
* resolution: => invalid
* needs_tests: => 0
* needs_better_patch: => 0

Comment:

Please see TicketClosingReasons/UseSupportChannels for ways to get help
with usage questions.