[TYPO3-core] RFC #12908: Bug: wrong distance between image rows [css styled content]

Ernesto Baschny [cron IT] ernst at cron-it.de
Thu Apr 22 16:12:32 CEST 2010


Susanne Moog schrieb am 22.04.2010 11:55:

>> The same rationale applies to this #12908: I wouldn't have commited it
>> to the 4.3 branch and in trunk not apply it to the v4.3 static
>> templates. Because this might BREAK existing sites on a minor update!
>> This is bad.
>>
>> These kind of stuff is a "change of behaviour" in my eyes, and should
>> require a major upgrade. A hint on how to solve it in older sites (by
>> adding specific CSS lines into the sites CSS) is enough for older sites.

> That would mean that we are not allowed to fix any css bugs for older
> CSS Styled Content versions. I mean, yes, fixing a bug can be considered
> changing behavior because it certainly should behave not buggy
> afterward... We can agree that CSS bugs are not considered "real" bugs
> and therefore not fixed in minor versions, but then we have to clearly
> communicate it that way, in the bug tracker, in the manual, I don't
> know... Don't get me wrong, I understand your concern, but I still think
> it is hard to communicate.

Or course we never intentionally want to add a regression bug in another
fix, but in the case of CSS hacks being applied in the frontend, I can
imagine that almost every change will make the one or another site
behave differently. You cannot test it all, even if in "your site" it
works on all browsers in the world. There are tons of side effects that
are caused by site specific CSS that one cannot predict.

So regarding css_styled_content's default "CSS" I am for this rule:

- no CSS changes for the frontend in minor versions updates,
- CSS fixes and tweaks only in trunk and only on the main setup.txt. Old
"vX.Y/setup.txt" always remain untouched.
- compatVersion information on upgrade stating what has changed, so that
the user can specifically check if he is affected if he installs the new
setup.txt from the new major release after the upgrade.

As we only provide default CSS for "Text with images", this is the only
"beast" where this rules apply for now. And I doubt that we will provide
default CSS for other elements in future in CSC.

If someone needs a specific fix "backported" to an older version, the
bug report can add instructions on how to add them (usually some
TypoScript lines to add to your main template).

Cheers,
Ernesto


More information about the TYPO3-team-core mailing list