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
Right now, textContent doesn't do anything special, and one needs to use mdContent to re-render Markdown on the component.
However, that means that <md-block> doesn't work well with libraries that handle HTML in an agnostic way (e.g. Mavo, Vue, Angular etc).
However, if textContent (and innerText?) becomes an alias to mdContent, then how does one get the actual textContent of the element?
Another alternative would be if textContent sets mdContent on write, but returns the actual element textContent on read. This would allow libraries that work with textContent to update its content, but reading textContent would still work.
Is there any precedent for such behavior? Is it confusing?
The text was updated successfully, but these errors were encountered:
Right now,
textContent
doesn't do anything special, and one needs to usemdContent
to re-render Markdown on the component.However, that means that
<md-block>
doesn't work well with libraries that handle HTML in an agnostic way (e.g. Mavo, Vue, Angular etc).However, if
textContent
(andinnerText
?) becomes an alias tomdContent
, then how does one get the actual textContent of the element?Another alternative would be if
textContent
setsmdContent
on write, but returns the actual element textContent on read. This would allow libraries that work withtextContent
to update its content, but readingtextContent
would still work.Is there any precedent for such behavior? Is it confusing?
The text was updated successfully, but these errors were encountered: