When virtualizing an <img>, the src attribute is interpreted as an attribute. But Html.Attributes.src is a property.
This inconsistency confuses _VirtualDom_diffFacts, which generates a patch to delete the attribute and add the property, resulting in a visible flick on Firefox 62 (with developer tools closed). Chrome 69 seems to handle it fine, and I don't have a different browser to test on handy.
Would a patch adding an attribute -> property mapping to virtualize, at least for the properties available in Html.Attributes, make sense?
When virtualizing an
<img>
, thesrc
attribute is interpreted as an attribute. ButHtml.Attributes.src
is a property.This inconsistency confuses
_VirtualDom_diffFacts
, which generates a patch to delete the attribute and add the property, resulting in a visible flick on Firefox 62 (with developer tools closed). Chrome 69 seems to handle it fine, and I don't have a different browser to test on handy.Would a patch adding an attribute -> property mapping to
virtualize
, at least for the properties available inHtml.Attributes
, make sense?