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
I see multiple issues (#312, #227, #505, #594, #600) related to attr_list applied to table, ol or ul and I can't figure out if we settle on a specific syntax. Looking at the code it's not obvious if it's possible to assign class to ol/ul.
If not supported, I'm wondering why. Clearly, it's a highly requested feature and I see multiple proposal for syntax and implementation.
If supported, what is the right syntax ? and may we get this documented on the web site.
Thanks !
The text was updated successfully, but these errors were encountered:
I don't know what is so confusing. Sure, various non-members have proposed various solutions on the cited issues. However, my position has remained constant. Regarding lists I explain that:
...the markdown syntax has no concept of a ul or ol. They are simply implied by the fact that we have list items.
...how would one differentiate between attributes defined on a row, or on a table. The syntax only defines the cells, the rows and table are inferred.
It is not possible to assign attributes to elements which don't actually exist in the document. Therefore, we will never attempt to support such a feature, regardless of how many requests or proposals we receive. Of course, anyone is free to create their own extensions which have any behavior they want.
This is being closed as another duplicate of #227 and #312.
I see multiple issues (#312, #227, #505, #594, #600) related to
attr_list
applied to table, ol or ul and I can't figure out if we settle on a specific syntax. Looking at the code it's not obvious if it's possible to assign class to ol/ul.If not supported, I'm wondering why. Clearly, it's a highly requested feature and I see multiple proposal for syntax and implementation.
If supported, what is the right syntax ? and may we get this documented on the web site.
Thanks !
The text was updated successfully, but these errors were encountered: