I want this feature too!!!
Provide the thought:
Generate the html and insert in the markdown.
For example:
<table>
<tr>
<th>Advantages</th>
<th>Disadvantages</th>
</tr>
<tr>
<td>
<h3>First Aspect</h3>
<ul>
<li>First Advantage</li>
<li>Second Disadvantage</li>
</ul>
<h3>Second Aspect</h3>
</td>
<td>
<ol>
<li>First Disadvantage</li>
<li>Second Disadvantage</li>
</ol>
</td>
</tr>
</table>
A lot of features “would be nice” to have but are hard to add, because markdown tables are fragile.
The best way to add checkmarks is Benjamins suggestion, 3 posts above. In other words, add emoji checkmarks. You can use Autokey or Espanso to add these emojis on desktop devices.
Hey everyone! 
I just wanted to share that I’ve enhanced the existing “Check Please!” plugin to add support for multiple checkboxes per cell - solving this long-standing request without any weird syntax or workarounds. Add support for multiple interactive checkboxes per table cell by friebetill · Pull Request #2 · DevAndrewGeorge/obsidian-check-please · GitHub
The plugin now intelligently handles multiple checkboxes in the same cell - when you click one, it only toggles that specific checkbox and leaves the others unchanged. It uses smart context matching to ensure it updates the correct checkbox in the underlying markdown.
Best part: Your markdown files stay completely portable - they’re just normal markdown checkboxes that work perfectly in other editors too!
This enhancement finally enables the complex checkbox workflows many of us have been wanting in tables. No more need for emoji workarounds - you can now have proper, native checkbox functionality with multiple items per cell! 
+1 would love to see this
Just want to add my two cents. I would like to see this as well
+1 also would love to see this implemented!
@friebetill the plug in does not work in v.1.9.14, “fail to load”, do you have plan to update?
Bump.
Tables in Obsidian, or the basic implemention of markdown of Obsidian in general, is very limited compared to others alternatives on the market like Notion, Standard Notes, Notesnook, etc…
Sure, tables are fragile. But from a commerical-ish product I expect them to internally test markdown rendering to smithereens. It’s actually really rather easy to write unit tests for a 1000 different scenarios, and keep them running while working on the tables feature. This ensures that every supported syntax around them, won’t break when extending or modifying it.
So yes, fragile, but not as in “guaranteed to break”. Rather as in “important to test well”.
Agreed.
I tried to say, since Obsidian is like a multifaceted diamond, some stuff requires particular coding and designing knowledge.
Sometimes we really need some bigger break to archive progress, otherwise we may struggle indefinitely, especially with difficult features.
It isn’t just about adding checkboxes. Markdown tables by itself aren’t robust, imo.
+1. Add support for checkboxes in tables or adopt other Markdown flavors (using a flavor indicator in the header or footer for the renderer). I believe GitHub supports checkboxes in tables.
+1 
