Community discussions
It seems that tables with both width and column-width attributes ignore both attributes, unless I am doing something entire wrong. I am pretty sure this used to work and I did not change the tables. Example:
{ width: 100%, column-widths: "25% 25% 50%"}
| Characteristic | Perceived Opposite | Enabling Mechanism |
If I only specify width, the width renders as specified.
I can probably get by for now by removing column-widths, but it'd be great if someone can check. Thank you!
We'll investigate ASAP. Assuming this is real, chances are it will be fixed later today. I'll follow up as soon as I know more.
Hi Gregor,
Short version:
I have a bug fix being tested right now and shipping later today, but as a workaround if you remove the leading space it will work:
{width: 100%, column-widths: "25% 25% 50%"}
Long version:
We can confirm we have reproduced this issue, and it is a bug on our end. Thank you for the clear example.
Since a parser change in mid-June, a table attribute list written with a space after the opening brace and more than one attribute, like { width: 100%, column-widths: "25% 25% 50%"}, was being misread as a Markua document settings hash instead of table attributes, so the table silently lost both. A single attribute like { width: 100%} did not trigger this, which is why width on its own kept working.
We have fixed this, and the fix should be deployed later today. After that, the next preview or publish will pick it up with no changes needed to your manuscript.
If you want to generate before the fix is live, removing the space after the opening brace works right now:
{width: 100%, column-widths: "25% 25% 50%"}
Sorry again about these issues. If you have any questions or need anything else, please let us know.
Peter
Thank you!
Luckily, the automatic column width generation improved, so I can almost get away without custom sizing.