TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692024-02-13T11:10:01ZTYPO3 Forge
Redmine 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 #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 #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 #92298 (Closed): phpstan related changes to DependencyInjection caused wrong ty...http://forge.typo3.org/issues/922982020-09-13T06:55:53ZBenjamin Franzkeben@bnf.dev
<p><a class="external" href="https://review.typo3.org/c/Packages/TYPO3.CMS/+/65685">https://review.typo3.org/c/Packages/TYPO3.CMS/+/65685</a></p>
<p>In ServiceProviderRegistry::create Package argument was changed to PackageInterface,<br />but the method getServiveProvider() is not available on the Interface.<br />Package was declared as type (instead of PackageInterface) by intent.</p> TYPO3 Core - Bug #92239 (Closed): SymfonyEventDispatcher is not symfony/event-dispatcher-contract...http://forge.typo3.org/issues/922392020-09-09T12:09:37ZBenjamin Franzkeben@bnf.dev
<p><b>Fatal error</b>: Declaration of TYPO3\CMS\Core\Adapter\SymfonyEventDispatcher::dispatch(object $event, ?string $eventName = NULL): object must be compatible with Symfony\Contracts\EventDispatcher\EventDispatcherInterface::dispatch($event) in <b>[…]typo3/sysext/core/Classes/Adapter/SymfonyEventDispatcher.php</b> on line <b>26</b><br /></p>
<p><a class="external" href="https://bamboo.typo3.com/browse/CORE-GTN-229">https://bamboo.typo3.com/browse/CORE-GTN-229</a></p> TYPO3 Core - Bug #91398 (Closed): Serialization of ObjectManager is brokenhttp://forge.typo3.org/issues/913982020-05-14T13:11:34ZBenjamin Franzkeben@bnf.dev
<p>This is broken in v10 since the introduction of dependency injection in:<br /><a class="external" href="https://review.typo3.org/c/Packages/TYPO3.CMS/+/58255">https://review.typo3.org/c/Packages/TYPO3.CMS/+/58255</a></p>
<p>Using:<br /><pre>
serialize($this->objectManager)
</pre></p>
<p>Results in the following exception:</p>
<pre>
(1/1) Exception
Serialization of 'Closure' is not allowed
</pre> TYPO3 Core - Bug #91316 (Closed): MetaTagManagerRegistry instance not unique in uncached pluginshttp://forge.typo3.org/issues/913162020-05-06T09:04:27ZBenjamin Franzkeben@bnf.dev
<p>Reported by Aristeidis Karavas (Apr 28th at 11:51) via Slack:<br /><a class="external" href="https://typo3.slack.com/archives/C025BQLFA/p1588067478426300">https://typo3.slack.com/archives/C025BQLFA/p1588067478426300</a></p>
<blockquote>
<p>Why in TYPO3 v10 this won't set the meta tags in frontend?<br />$metaTag = $this->metaTagManagerRegistry->getManagerForProperty($key);<br />$metaTag->addProperty($key, $metaTagValue);<br />If i debug it, it sets everything right but it won't be displayed in the frontend</p>
</blockquote>
<p>The reason is that the PageRenderer stores a new Singleton via <code>GeneralUtility::setSingletonInstance</code> in <code>__wakeup</code>.</p>
<p>That updates <code>MetaTagManagerRegistry</code> instances retrieved via <code>GeneralUtility::makeInstance</code>, but not those injected via symfony DI,<br />where the object will already have been generated, as it is loaded during EXT:seo/ext_localconf.php loading and GeneralUtility::makeInstance<br />will call the DI container.</p>
<p>This issues happens when the PageRenderer was serialized and is unserialized for <code>USER_INT</code> plugins (e.g. uncached extbase plugins).</p>
<p>Same applies to AssetCollector, which is serialized and unserialized as well.</p> TYPO3 Core - Bug #89891 (Closed): Temporary assets can not be removed in install tool, exception ...http://forge.typo3.org/issues/898912019-12-06T22:37:42ZBenjamin Franzkeben@bnf.dev
<p>Exception is:</p>
<p>Too few arguments to function TYPO3\CMS\Core\Resource\ResourceFactory::__construct(), 0 passed in […]/typo3/sysext/core/Classes/Utility/GeneralUtility.php on line 3461 and exactly 1 expected</p>
<p>Solution:<br />The ResourceFactory needs to be defined by a service provider to be available in install tool mode.</p> TYPO3 Core - Bug #88808 (Closed): Warning in AbstractConfigurationManagerTesthttp://forge.typo3.org/issues/888082019-07-19T20:45:19ZBenjamin Franzkeben@bnf.dev
<pre>
TYPO3\CMS\Extbase\Tests\Unit\Configuration\AbstractConfigurationManager
⚠ Controller of switchable controller actions can be a fully qualified class name
┐
├ Trying to configure method "getSwitchableControllerActions" which cannot be configured because it does not exist, has not been specified, is final, or is static
│
</pre> TYPO3 Core - Task #87742 (Closed): Use real ObjectManager stubs in unit testshttp://forge.typo3.org/issues/877422019-02-19T12:19:14ZBenjamin Franzkeben@bnf.dev
<p>Prevent invocation of the constructor (which instantiates<br />an internal instance of the extbase container) and do not<br />mix usage of mocked and stubbed methods.</p>
<p>The mixture happened due to using setMethods(['get']) – where<br />all other methods (besides 'get()') are actually proxied to the<br />real ObjectManager.</p> TYPO3 Core - Task #87741 (Closed): Mock SignalSlot\Dispatcher FileRepository Singletons in unit t...http://forge.typo3.org/issues/877412019-02-19T12:17:22ZBenjamin Franzkeben@bnf.dev
<p>Prevent indirect ObjectManager invocation by mocking FileRepository.</p> TYPO3 Core - Task #87740 (Closed): Mock FileRepository Singletons in unit testshttp://forge.typo3.org/issues/877402019-02-19T12:16:03ZBenjamin Franzkeben@bnf.dev
<p>Prevent indirect SignalSlot\Dispatcher and ObjectManager<br />invocation by mocking FileRepository.</p> TYPO3 Core - Task #87739 (Closed): Mock ResourceFactory Singleton instantation in unit testshttp://forge.typo3.org/issues/877392019-02-19T12:14:28ZBenjamin Franzkeben@bnf.dev
<p>This prevents indirect SignalSlotDispatcher and ObjectManager<br />invocation by stubbing the ResourceFactory (or removing unneeded<br />mocks by preventing constructor invocation as in ImageServiceTest).</p> TYPO3 Core - Bug #87622 (Closed): Minimum required prophecy version is incompatible with object (...http://forge.typo3.org/issues/876222019-02-02T06:08:41ZBenjamin Franzkeben@bnf.dev
<p>Recent changes like <a class="external" href="https://review.typo3.org/c/59600/">https://review.typo3.org/c/59600/</a> introduced <code>object</code> return type decarations which are only supported as of prophecy version 1.7.5.<br />This caused nightly, composer minimum builds, to fail: <a class="external" href="https://bamboo.typo3.com/browse/CORE-GTN-UT2PHP72-646">https://bamboo.typo3.com/browse/CORE-GTN-UT2PHP72-646</a></p>
<p>Therefore the default minimum – as required by phpunit (^1.7) – needs to be raised to 1.7.5.</p> TYPO3 Core - Bug #87229 (Closed): checkDataSubmission is missing in extension scannerhttp://forge.typo3.org/issues/872292018-12-19T20:05:14ZBenjamin Franzkeben@bnf.dev
<p>In <a class="issue tracker-4 status-5 priority-4 priority-default closed" title="Task: Deprecate hooks superseded by PSR-15 middlewares (Closed)" href="http://forge.typo3.org/issues/86279">#86279</a> checkDataSubmission slipped through and was forgotten to be mentioned in a .rst file and the extension scanner configuration.</p>