Page MenuHomePhabricator

No way to have an empty row in a remarkup table
Closed, ResolvedPublic

Description

Blank rows in tables can be useful to create a separation between parts of a table. However, the Remarkup parser seems to remove them from the rendered table.

| Category A | |
| Item A.1 | 100 |
| Item A.2 | 200 |
| **Total Category A** | 300 |
| | |
| Category B | |
| Item B.1 | 250 |
| **Total Category B**| 250 |
| | |
| **Total** | 550 |
Category A
Item A.1100
Item A.2200
Total Category A300
Category B
Item B.1250
Total Category B250
Total550
phabricator 5885704800a97aadf47aee5654ff2647b40fb4ad (Sat, Jun 10) (branched from 3400f24c8b53a742b6dd39a9c244f45c51db85ac on origin)
arcanist 0c53a35d30e924f902510eb2e497ae5934209304 (Fri, Jun 9) (branched from c04f141ab0231e593a513356b3832a30f9404627 on origin)
phutil 612619d0040b5e13c4e068dce443217abbc10a00 (Fri, Jun 9) (branched from 74a1350416eb2df825c2315d6519bee03f77bee9 on origin)

Event Timeline

avivey renamed this task from Remarkup parser ignores blank table rows to No way to have an empty row in a remarkup table.Jun 17 2017, 1:46 AM
avivey moved this task from Backlog to Tables on the Remarkup board.

Unicode Zero Width Space to the rescue!

Category A
Item A.1100
Item A.2200
Total Category A300
Category B
Item B.1250
Total Category B250
Total550
epriestley added a subscriber: epriestley.

I'm not really sold on this use case, but I think the result is unintuitive/buggy enough to fix anyway.