Actions
Bug #91644
closedcssInline non closing comment affects following css
Status:
Rejected
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2020-06-15
Due date:
% Done:
0%
Estimated time:
TYPO3 Version:
9
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:
Description
In a setup with more than one cssInline data an issue occurs when a non closing css comment is used within a css definition that is not last.
'Hard' to describe, easy to understand with code and screenshot.
cssInline { 1 = TEXT 1.value ( .inlineCssComment { display: block; } /* currently unused, but maybe needed later on. .foobar { display: block; } ) 2 = TEXT 2.value ( .test { display:block; } .test2 { display: block; } ) }
results in
<style type="text/css" id="inline-css"> /*additionalTSFEInlineStyle*/ .inlineCssComment { display: block; } /* currently unused, but maybe needed later on. .foobar { display: block; } .test { display:block; } .test2 { display: block; } </style>
which disables all classes below the opening comment
Files
Updated by Georg Ringer over 4 years ago
- Status changed from New to Rejected
rejected because it is a mistake by the user. unless TYPO3 would parse the whole inline CSS it is impossible to detect any mistakes
Actions