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
If any mf2 classnames are found in a document, don’t convert any classic mf classnames
E.G. currently parsing this URL with classic support turned on produces bad results due to classic mf classnames being on different elements to mf2 classnames — with stricter checking this would not be a problem.
The text was updated successfully, but these errors were encountered:
Resolved in v0.2.0 with improved (more spec-compliant) classic mf support. I’m leaving convert classic on by default to help root out bad markup, it shouldn’t be so much of a problem now.
If any mf2 classnames are found in a document, don’t convert any classic mf classnames
E.G. currently parsing this URL with classic support turned on produces bad results due to classic mf classnames being on different elements to mf2 classnames — with stricter checking this would not be a problem.
The text was updated successfully, but these errors were encountered: