removing unnecessary max-width on tables

[bcullman]

From the history, it appears max-width was added to tables.less when various css declarations originating in reset.less were relocated to appropriate less files so that reset.less could be removed in favor of normalize.less.

However, this max-width declaration did not come from Eric Meyer's reset.less. Instead, it was added in the following check-in by @mdo "help tables not look like shit on mobile maybe?"

97b2858

I don't believe that this declaration has proven it helps layouts on mobile. However it does cause layout problems when using bootstrap in conjunction with other javascript libraries.

If the original implementation was iffy to begin with, lets just remove it.

[cvrebert]

However it does cause layout problems when using bootstrap in conjunction with other javascript libraries.

Do you have an example of this?

[bcullman]

I am using bootstrap in a legacy app that also uses an old version of extJS for some parts of the UI.

extJS builds nearly all of their widgets with non-semantic HTML (aka tables). When doing re-size calculations, table elements are returning the value "1" for width value rather than the correct width in pixels, and this is due to the max-width statement on table in bootstrap.

I won't argue that this is due to a bug in the old extJS implementation - it likely is.

However when reviewing the Bootstrap history, it looks like this max-width statement was erroneously added.

[cvrebert]

It's also weird that we are applying this CSS to all <table> elements rather than just to the .table class.