> It's 50 lines of CSS […] there's absolutely 0 technical reason to not add this.
That's not true at all. You suggest to add an option for _one_ interface change because only a few lines CSS are needed. But the next one want another UI customization, maybe even five lines less CSS. And suddenly there are requests for 3,000 customizations and this sums up. You should also remember that's not only about an one-time investment of resources. It needs an permanent comittment to consider every possible configuration on every frontend change.
Don't get me wrong. I'm not arguing for or against an option for this change. But your argument that it's only a few lines CSS and there is not reason not to do this doesn't hold up.
Bug 1561531 Comment 87 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
> It's 50 lines of CSS […] there's absolutely 0 technical reason to not add this.
That's not true at all. You suggest to add an option for _one_ interface change because only a few lines CSS are needed. But the next one want another UI customization, maybe even five lines less CSS. And suddenly there are requests for 3,000 customizations and this sums up. You should also remember that's not only about an one-time investment of resources. It needs an permanent comittment to consider every possible configuration on every frontend change.
Don't get me wrong. I'm not arguing for or against an option for this change. But your argument that it's only a few lines CSS and there is no reason not to do this doesn't hold up.
> It's 50 lines of CSS […] there's absolutely 0 technical reason to not add this.
That's not true at all. You suggest to add an option for _one_ interface change because only a few lines CSS are needed. But the next one want another UI customization, maybe even five lines less CSS. And suddenly there are requests for 3,000 customizations and this sums up. You should also remember that's not only about an one-time investment of resources. It needs an permanent comittment to consider every possible configuration on every frontend change.
Don't get me wrong. I'm not arguing for or against an option for this change. But your argument that it's only a few lines CSS and there is no reason not to do this does not work.