nov 16 2013 18.07 Chris Rockwell: > The JavaScript is necessary in Chris' solution because the height needs to be > set in something other than percentage or auto to get the added element (div > or otherwise) to fill the td vertically. > >
Good catch. > I agree that in some cases it could be a "design smell", but, if the link is > important it could be considered an enhancement to position them all > similarly. For instance, a "see more" link when a table cell is displaying > teaser like data. In other words, there are perfectly valid reasons for > wanting to position something within a table cell > > Except that to position the link inside the table cell isn't the only solution, Why not on a new row for instance? Why must the link belong on the exact same row? I don't see that. Sometimes you may have to resort to scripting for good reasons, but commonly I try and rethink what I'm doing in that case. I've found in my experience this type of thing only creep up on me when I don't have the proper control over the design ideas that must be implemented. I had a scrolling column design once which controls just "had to" have the same look on all platforms and the only way to do that then — known to me at least — was to get some scripts for the controls. I still thought this was unwise and in the end I also couldn't use that site for my portfolio. Everyone loses from such situations. ______________________________________________________________________ css-discuss [[email protected]] http://www.css-discuss.org/mailman/listinfo/css-d List wiki/FAQ -- http://css-discuss.incutio.com/ List policies -- http://css-discuss.org/policies.html Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
