I was going to report that when tabbing on the first empty column, the row is indented. about advanced-tables-obsidian

[kristynlynn]

Just a note that if these are expected changes and not a bug, the readme needs to be updated. The "How to use" section still describes the old behavior, leading me to think I was doing something wrong. I think the demo graphic needs to be updated too.

To create a table, create a single | character, then type the table's first heading and press Tab. Continue entering headings and pressing Tab until all the headings are created. Press Enter to go to the first row. Continue filling cells as before, and press Enter again for each new row.

[Scofield-Gu]

me too.
My solution: change to source mode and the advanced table plugin may work.
If the table has been completed, switch back to the live preview

[jarchiepacheco]

The behavior has changed with this version. Now you need to type a bit more of the table before the plugin recognizes that you are in a table. More info

This solved it for me. Thank you so much

[jarchiepacheco]

I am currently having the same issue. Doing | name just indents inwards when I press tab, it doesn't actually create a table.

• Windows 11
• Obsidian Version 1.5.3
• Advanced tables version 0.20.0

[premedios]

Also having the same issue

• MacOS Ventura 13.6.3
• Obsidian 1.5.3
• Advanced tables version 0.20.0

[sun2ot]

Me too.

• Windows 11
• Obsidian Version 1.5.3
• Advanced tables version 0.20.0

[outsu]

Same issue.

• Windows 11
• Obsidian v1.5.3
• Advanced Tables v0.20.0

[khorton]

The behavior has changed with this version. Now you need to type a bit more of the table before the plugin recognizes that you are in a table. More info

[premedios]

Solved here as well

[deltabrav0]

I am having the same issue after updating. Regardless of number of characters, plugin does not recognize table.

[deltabrav0]

Changing to source mode did not work for me. Regarding "typing a bit more" How much more? Is that referring to text after the first pipe or second, etc.

[khorton]

See the link in my original comment

[BingeCode]

Just a note that if these are expected changes and not a bug, the readme needs to be updated. The "How to use" section still describes the old behavior, leading me to think I was doing something wrong. I think the demo graphic needs to be updated too.

Commenting to point out that this still needs to be done. The instructions are still outdated and cost a lot of time to figure out the issue. Frustrating for first time users.

[nmlynch94]

Same issue here. The README instructions are wrong for the current version. I would offer a PR, but I'm unclear on what the expected process is to be after the update that changed this, or if it was even supposed to change.