TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692024-03-26T08:54:11ZTYPO3 Forge
Redmine TYPO3 Core - Task #103485 (Under Review): Provide lib.parseFunc via ext:frontendhttp://forge.typo3.org/issues/1034852024-03-26T08:54:11ZBenjamin Franzkeben@bnf.devTYPO3 Core - Bug #103444 (Resolved): YamlFileLoader has no logger instancehttp://forge.typo3.org/issues/1034442024-03-21T04:31:37ZBenjamin Franzkeben@bnf.dev
<p>Uncaught TYPO3 Exception Call to a member function error() on null<br />thrown in file /home/ben/src/TYPO3.CMS/typo3/sysext/core/Classes/Configuration/Loader/YamlFileLoader.php<br />in line 171</p> TYPO3 Core - Task #103287 (Resolved): Revert "[TASK] Format fluid format tags consistently"http://forge.typo3.org/issues/1032872024-03-05T14:32:10ZBenjamin Franzkeben@bnf.dev
<p>The patch has been merged with too few votes.</p> TYPO3 Core - Task #103109 (Resolved): Important-102799-TYPO3_CONF_VARSGFXprocessor_stripColorProf...http://forge.typo3.org/issues/1031092024-02-13T11:10:01ZBenjamin Franzkeben@bnf.dev
<p>One patchset was missing from <a class="external" href="https://review.typo3.org/c/Packages/TYPO3.CMS/+/82940">https://review.typo3.org/c/Packages/TYPO3.CMS/+/82940</a> that had been forget to be updated to updates on the main branch.</p> TYPO3 Core - Task #101483 (Closed): Revert "[!!!][TASK] Introduce type declarations in AbstractFile"http://forge.typo3.org/issues/1014832023-07-29T07:52:20ZBenjamin Franzkeben@bnf.dev
<p>There were errors in CI that have not been catched properly.</p> TYPO3 Core - Bug #101482 (Resolved): Mariadb acceptance test error detection not workinghttp://forge.typo3.org/issues/1014822023-07-29T07:43:51ZBenjamin Franzkeben@bnf.dev
<p>See <a class="external" href="https://typo3.slack.com/archives/C03AM9R17/p1690614726567099?thread_ts=1690593575.789689&cid=C03AM9R17">https://typo3.slack.com/archives/C03AM9R17/p1690614726567099?thread_ts=1690593575.789689&cid=C03AM9R17</a></p> TYPO3 Core - Task #101481 (Closed): Revert "[!!!][TASK] Add native type declarations to GU array...http://forge.typo3.org/issues/1014812023-07-29T07:42:45ZBenjamin Franzkeben@bnf.dev
<p>CI test failures were not catched properly.</p> TYPO3 Core - Bug #101480 (Resolved): Invalid null coalescing fallback to boolean in record listhttp://forge.typo3.org/issues/1014802023-07-29T06:59:54ZBenjamin Franzkeben@bnf.dev
<p>Causes an error since <a class="issue tracker-4 status-5 priority-4 priority-default closed" title="Task: Add native type declarations to GU array methods (Closed)" href="http://forge.typo3.org/issues/101453">#101453</a></p>
<pre><code>Core: Exception handler (WEB: BE): TypeError, code #0, file /builds/typo3/CI/cms/typo3/sysext/core/Classes/Utility/GeneralUtility.php, line 801: TYPO3\CMS\Core\Utility\GeneralUtility::trimExplode(): Argument #2 ($string) must be of type string, bool given, called in /builds/typo3/CI/cms/typo3/sysext/backend/Classes/RecordList/DatabaseRecordList.php on line 2242- TypeError: TYPO3\CMS\Core\Utility\GeneralUtility::trimExplode(): Argument #2 ($string) must be of type string, bool given, called in /builds/typo3/CI/cms/typo3/sysext/backend/Classes/RecordList/DatabaseRecordList.php on line 2242, in file /builds/typo3/CI/cms/typo3/sysext/core/Classes/Utility/GeneralUtility.php:801 -</code></pre> TYPO3 Core - Task #101464 (Closed): Reactivate usage of constructable stylesheets for icon elementhttp://forge.typo3.org/issues/1014642023-07-27T19:41:48ZBenjamin Franzkeben@bnf.dev
<p>With <a class="issue tracker-4 status-5 priority-4 priority-default closed" title="Task: Streamline icon elements (Closed)" href="http://forge.typo3.org/issues/100270">#100270</a> stylesheets in icon elements have been inlined<br />instead of using lit's own style wrapper that uses constructable<br />stylesheets if available.<br />Inline stylesheets need to be parsed over and over again, whenever<br />a web component is used multiple times.<br />The icon element is supposed to be used very often, which is why this<br />matters. Constructable stylesheets are cached and therefore do only<br />need to be parsed once, regardless how often a web component is used.</p> TYPO3 Core - Bug #101288 (Resolved): sudo-mode opens module contents without backend frame when u...http://forge.typo3.org/issues/1012882023-07-07T13:08:44ZBenjamin Franzkeben@bnf.devTYPO3 Core - Task #101265 (Closed): Update docs to refer to ES6 modules instead of RequireJShttp://forge.typo3.org/issues/1012652023-07-06T14:30:36ZBenjamin Franzkeben@bnf.devTYPO3 Core - Task #99580 (Closed): Increase clickable panel-heading touch/click-areahttp://forge.typo3.org/issues/995802023-01-17T16:43:47ZBenjamin Franzkeben@bnf.dev
<p>Current click-area height is 13px, so the padding-area of the panel-heading isn't clickable to toggle collapse.</p>
<p><img src="http://forge.typo3.org/attachments/download/37321/panel-link-size-v2.png" alt="" loading="lazy" /></p> TYPO3 Core - Task #97319 (Closed): Revert "[TASK] Refresh the look of pagemodule"http://forge.typo3.org/issues/973192022-04-06T13:40:00ZBenjamin Franzkeben@bnf.dev
<p>Reason for revert:</p>
<ul>
<li>Invasive change that was merged too quickly</li>
<li>Missing commit message description
* No description of the global scope/direction.<br /> Will the new style be applied to <strong>all</strong> backend<br /> interfaces? And who will feel responsible?
* Deserves an epic on forge</li>
<li>Missing credits to structured content initiative</li>
<li>Quality issues:
* Delete button removal does not have broad acceptance
* Inconsistent border radii for content elements and grid cells
* Inconsistent elevation (box-shadow) for elements and grid cells</li>
</ul> TYPO3 Core - Bug #97144 (Closed): Slow module scrolling in Google Chrome on Linuxhttp://forge.typo3.org/issues/971442022-03-08T15:09:57ZBenjamin Franzkeben@bnf.dev
<p>Scrolling the list module with 100 entries causes FPS to drop to <15fps on Google Chrome (v99) with Linux during scrolling.<br />This is for sure a Chrome Bug, but reveals that <code>overflow: hidden</code> and <code>scrolling="no"</code> on the module iframe is not a good idea.</p>
<p>It would be great to remove the <code>scrolling="no"</code> parameter from the module iframe and enable scrolling on <html> instead of .module-body</p>
<p>There are some past issues to take into account when changing the module-scrolling semantics: <a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: Correct horizontal scrolling in iOS browsers (Closed)" href="http://forge.typo3.org/issues/83841">#83841</a> <a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: rte_ckeditor displaces dropdown overlays and jumps to top of page on crome/safari (Closed)" href="http://forge.typo3.org/issues/80116">#80116</a> <a class="issue tracker-1 status-5 priority-6 priority-high2 closed" title="Bug: RTE CKeditor top-positioning for maximize and combopanels is broken in browsers with webkit (Closed)" href="http://forge.typo3.org/issues/82780">#82780</a></p>
<p>Using overflow: auto on <code><html></code> as suggested in <a class="external" href="https://forge.typo3.org/issues/80116#note-7">https://forge.typo3.org/issues/80116#note-7</a> was mainly avoided because of mobile iOS overscroll behaviour, otherwise this could have already been changed with: <a class="external" href="https://review.typo3.org/c/Packages/TYPO3.CMS/+/55647">https://review.typo3.org/c/Packages/TYPO3.CMS/+/55647</a></p>
<p>Consider using the standardized <code>overscroll-behaviour</code> property to fix issues on that part.</p> TYPO3 Core - Task #96725 (Closed): Use generics for ObjectProphecy class propertieshttp://forge.typo3.org/issues/967252022-02-01T15:52:33ZBenjamin Franzkeben@bnf.dev
<p>With <a class="issue tracker-1 status-5 priority-4 priority-default closed" title="Bug: Fix incorrect Prophecy usages (Closed)" href="http://forge.typo3.org/issues/96713">#96713</a> all type annotations on class properties<br />in tests have been reduced to ObjectProphecy only,<br />removing the information which class or interface<br />is mocked.</p>
<p>The jangregor/phpstan-prophecy plugin defines ObjectProphecy<br />as a generic tag, allowing generics to be used and<br />resolved by PHPStan. Therefore the type annotations<br />on class properties or function results are now re-added.</p>