In response to this:
The notwide parameter is used to avoid huge amounts of whitespace in tables, and likewise the float parameter is used when tables are small enough to fit off to the side. The information filled both tables to 100%, so collapsing them wasn't doing anything. Whitespace issues above and below the table should be handled in those sections. In this case, I think moving the left image below the bullets and sizing down the right image would fix things. Let me know if this change looks better to you. — najzere 10:42, 26 August 2009 (UTC)
Yes and no. It does cut down on whitespace, but I wanted to eliminate it completely. By using the notwide parameter it reduces the whitespace on the page to nil and as far as I can tell doesn't change the table at all apart from maybe adding one more line of text in one of the cells. —The preceding unsigned comment was added by Calicoo (talk • contribs) .
- The way it was before created whitespace for me – all along the right side of the table below the image on the right. Full width tables are used precisely to combat to what you want to avoid: whitespace. To answer your question, no, there's no policy or rule governing when to use
notwideandfloat, there's just a line in the guide saying that "in most cases" you'd want to use full width and the general style found throughout the wiki. What I can say is that if the contents of a table fill out the entire width of the page (or more), then not specifying full width allows elements to look like they're running into each other when one is floated to the side of the table. That being said, I don't have a very strong opinion on this, so unless Prod or DrBob want to comment on what our actual table styles are (unlikely), I doubt you'd meet much resistance if you changed it back, other than people periodically coming in to "clean up" the page if they stumble upon it. — najzereT 15:25, 26 August 2009 (UTC)
The way it was before created whitespace for me – all along the right side of the table below the image on the right. That's how it was for me as well. To me it looks better like that. Either way is fine though. I was just trying to make everything flow without gaps in between a data. I'll leave it for now and when more is added to or taken away from the page we'll then decide what to do with it.
Calicoo 15:38, 26 August 2009 (UTC)
- The optimal time to use "notwide" is when you can create whitespace where content can fit (as Naj said, when it "allows elements to look like they're running into each other when one is floated to the side of the table"). As such, don't use notwide if the information on the page hasn't been lined up, there isn't enough content to fit on the side, or if in doing so, the table extends excessively far down the page. It's a matter of keeping things concise. --Notmyhandle (talk • contribs) 16:59, 26 August 2009 (UTC)