@Roach Thanks for weighing in.
Man, I forgot that the table cells support a weird "active" / "success" / "danger" / etc parameter.

I had to go look in the code to even remember what you were referring to. Yeah, those are terrible and thankfully undocumented.
I'm open to pretty much all of these. Here's how implementable I think they are.
Image align: Planned
[img align=left|right] -- Float the image left or right text reflow (aka CSS float property)
I like this and it should be simple to implement. Though presumably there might need to be some sort of float-clear tag?
developer.mozilla.org/en-US/docs/Web/…Image resize: Needs work
[img width=200] [img height=200] -- Keep aspect ratio the same by change one dimension
[img=100x200] -- Hard-code image resize.
While it's obviously useful, the downside of image resize is that it makes it easy to grab some massive image and resize it to 200px x 200px so that it secretly wastes bandwidth. I'm not sure how to handle that. At least with the current system, it's obvious when you're accidentally using a huge image.
Edit: Actually I have a great idea for this.
Cell background color: Planned
I'll remove support for the current weird parameters like [cell=danger].
Swapping it out for [cell=#39b54a] seems reasonable.
Table/cell border color: Needs work
Not sure of the syntax on the cell vs table. Too niche to think about at the moment.
Text background color: Needs work
I suppose I could add [bgcolor={color}] for symmetry with [color={color}], but I'd need to think about unintended effects and how it interacts with other bbcode.
Horizontal scroll: Low priority
I'm open to ideas like [table nowrap] where table cells won't wrap which could allow the table to scroll when it overflows. But it's so niche that it's low priority.
Text shadows: Planned
I could create a bbcode tag that maps directly to CSS text-shadow:
developer.mozilla.org/en-US/docs/Web/…Check out the demo at the top of that link.