I'm not sure whether you would agree this is a bug, but on our systems we upgrade to 2.3 and that exposed this problem which wasn't there in previous versions.

Anyone using the Content Formatting Macro's on their site will suddenly find tables going very screwy as the

macro in the Compatibility Macros are suddenly kicking in, in favour of CFM's. As compatibility with snip-snap markup is less likely (at least in our experience) than the desire to generate flexible html using wiki markup, I would vote for disabling the Compatibility Macros plugin by default - which can be easily turned on.

I will file an issue for making macro clashes easier to detect separately here: CONF-7647