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
Update: there is no need for the inner, simply set html already shows the issue. Am I using it correctly in the proper namespace? I tried set html "<svg:g hhh=''/>" and that still won't do it.
I have a little snippet that behaves differently on IE11 and Firefox:
do test <-SVG.svg
inner <-SVG.circle
pure test # set html "<g hhh=''/>"#+ [pure inner]
pure body #+ [ UI.div#+ [pure test] ]
Note the absence of <g> in the former. This does not happen in IE when I add stuff to a <div> in the same manner.
Am I using set html ... correctly for adding elements to an <svg> tag? At least one SVG example advertises this way. Or is the IE11 (or the threepenny binding) buggy? Is Firefox buggy to accept this?
The text was updated successfully, but these errors were encountered:
Am I using set html ... correctly for adding elements to an tag? At least one SVG example advertises this way.
You should use the functions from the Graphics.UI.Threepenny.SVG.* modules, they use the correct namespace. Using set html is not recommended — it is called html, after all. 😅 Looks like a namespace issue, indeed, but I don't know how fix that.
Which example suggests set html? If it is in the Threepenny repository, I should probably remove it.
Update: there is no need for the
inner
, simplyset html
already shows the issue. Am I using it correctly in the proper namespace? I triedset html "<svg:g hhh=''/>"
and that still won't do it.I have a little snippet that behaves differently on IE11 and Firefox:
In IE11 I get as DOM:
while in Mozilla I get
Note the absence of
<g>
in the former. This does not happen in IE when I add stuff to a<div>
in the same manner.Am I using
set html ...
correctly for adding elements to an<svg>
tag? At least one SVG example advertises this way. Or is the IE11 (or the threepenny binding) buggy? Is Firefox buggy to accept this?The text was updated successfully, but these errors were encountered: