Thanks, Jon.

I cannot see how keeping the current behavior for webParts that have frames intact and creating the expected behavior for a webPart (just adding an extra custom class to its wrapper/parent), which has its frame config set to 'none', can cause other parts of the UI to fail. Unless, of course, the custom class is something wack, then the UI can fall apart, but that's up to the dev to specify the correct extra class...