Change Details

Resizing the browser on the interface triggers responsive design, but I think it's triggering too soon. It seems to be triggered based on the size of the "compare" link -- the first attachment shows the page just before the "elections-2013-results" runs into the buttons, the second pic shows the page after that collision triggers the responsive design. There's a couple things we could do -- reduce the font size on the link, and allow the link to wrap to a second line. What do you think?

The columns collide with unpleasant effects when the "compare" link bumps into the Review column. The first attachment shows the page just before the "elections-2013-results" runs into the buttons, the second pic shows the page after that collision triggers the responsive design. There's a couple things we could do -- reduce the font size on the link, and allow the link to wrap to a second line. What do you think?

Resizing the browser on the interface triggers responsive design, but I think it's triggering too soonThe columns collide with unpleasant effects when the "compare" link bumps into the Review column. It seems to be triggered based on the size of the "compare" link -- theThe first attachment shows the page just before the "elections-2013-results" runs into the buttons, the second pic shows the page after that collision triggers the responsive design. There's a couple things we could do -- reduce the font size on the link, and allow the link to wrap to a second line. What do you think?