Just wanted to say... I'm going to remove support for flex altogether. While it won't come as a surprise to you guys considering all the trouble I had with it, today I decided to search google for 'nested flexbox', which is what I'm doing in Wedge, and guess what..? The results tend to say that flexboxes are BUGGY when nested inside of each other. NO KIDDING...
Considering that browsers are "not ready" for that, then I see no reason to waste my time on it.
I quickly looked into the grid module as a replacement, as it offers full rowspan/colspan support and thus does exactly what I want, but it's only fully supported in IE10. I've read, here and there, that Chrome 27 "will" support it. However, Canary is currently at version 28, and there's still no such thing as proper support for "-webkit-grid-columns" or whatever... Also, Firefox has some -moz-grid properties, but they're for use in XUL only, so it doesn't apply to Wedge itself.
At this point, I'll just stick to the display:table layout, and after that, there are really only three solutions...
- Leave it be.
- Implement <table> tags, because I can. Not exactly responsive, though... But I can always replace the table tags with regular divs with macros for Wireless, or whatever. Wedge is powerful.
- Restore the quick JS function I wrote to harmonize cell sizes. This is the 'best' solution, but unfortunately, because it needs to load images and have 'definitive' sizes for cells before I start this, I can't run it at .ready() time, and thus have to rely on .load(), hence a very, VERY visible jump in cell size at page load time.
I don't know if it's worth doing a poll for this..? I suspect that I'm the only one who cares about cell size harmonization, or close to... (Then again, my tendency to work for days on a single minor feature no one cares about is also what gave birth to some excellent modules, such as Wess and, well, Wedge's skeleton and mini-skeleton systems...)
