| 3 | | Under some circumstances the columns may overlap by a few pixels, but I do "badly broken" would not be a fair characterization of the situation, which is an artifact of different rendering engines handling CSS differently; it does not occur universally. Regardless, it is central to the whole purpose of this patch: The *user* should have the power to control their dashboard display, as they did pre 3.4. If a user wishes to sacrifice a small amount of "beauty" for functionality, they should be able to do so. If a 4-column interface is too muddled for them with their particular browser and window-size, they can opt to use 3 columns. This allows more people more options, versus the situation inflicted on users since 3.4, in which those whom have the ability to display 4 columns well (see screenshots) are precluded from doing so by arbitrary constraints. |
| | 3 | Under some circumstances the columns may overlap by a few pixels, but I do not think "badly broken" would be a fair characterization of the situation, which is an artifact of different rendering engines handling CSS differently; it does not occur universally. Regardless, it is central to the whole purpose of this patch: The *user* should have the power to control their dashboard display, as they did pre 3.4. If a user wishes to sacrifice a small amount of "beauty" for functionality, they should be able to do so. If a 4-column interface is too muddled for them with their particular browser and window-size, they can opt to use 3 columns. This allows more people more options, versus the situation inflicted on users since 3.4, in which those whom have the ability to display 4 columns well (see screenshots) are precluded from doing so by arbitrary constraints. |
![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png){kind=logo}
