TYPO3 Forge: Issueshttp://forge.typo3.org/http://forge.typo3.org/themes/typo3_forge/favicon/favicon.png?17058661692022-07-08T08:57:25ZTYPO3 Forge
Redmine TYPO3 Core - Task #97873 (Closed): Named handlers in HTTP stackhttp://forge.typo3.org/issues/978732022-07-08T08:57:25ZMathias Brodalambrodala@pagemachine.de
<p>Since <a class="issue tracker-1 status-5 priority-3 priority-lowest closed" title="Bug: RequestFactory respects Guzzle Middleware/Handler configuration from TYPO3_CONF_VARS (Closed)" href="http://forge.typo3.org/issues/88871">#88871</a> one can add custom middlewares/handlers to the handler stack used by Guzzle within TYPO3 via <code>$GLOBALS['TYPO3_CONF_VARS']['HTTP']['handler']</code>.</p>
<p>These are pushed onto the handler stack without name. Chances are high that a name is available in the <code>$GLOBALS['TYPO3_CONF_VARS']['HTTP']['handler']</code> array so this should be pushed together with the middleware/handler.</p>
<p>Benefit: easier debugging.</p> TYPO3 Core - Task #96267 (New): Add dedicated error for class construction without dependencieshttp://forge.typo3.org/issues/962672021-12-07T09:29:03ZMathias Brodalambrodala@pagemachine.de
<p>Right now if <code>GeneralUtility::makeInstance()</code> is used to construct a class which uses constructor dependency injection and has not being marked as <code>public</code>, a low-level <code>\ArgumentCountError</code> is thrown by PHP.</p>
<p>This should be improved by catching this case and replacing the error with a custom one (e.g. <code>MissingDependenciesError</code>). Either that custom error already hints at possible solutions or its dedicated error code is used to link to the docs with more details. The docs could then suggest to mark the class as <code>public</code> or manually pass the dependencies as arguments.</p> TYPO3 Core - Task #89866 (Closed): Use new Typo3Copyright API everywherehttp://forge.typo3.org/issues/898662019-12-05T17:08:33ZMathias Brodalambrodala@pagemachine.de
<p>After <a class="issue tracker-4 status-5 priority-4 priority-default closed" title="Task: Move Copyright information generation out of TYPO3 Backend (Closed)" href="http://forge.typo3.org/issues/89756">#89756</a> there are still some locations which directly use e.g. the <code>TYPO3_copyright_year</code> constant and should be migrated to the <code>Typo3Copyright</code> class.</p> TYPO3 Core - Task #89761 (New): Optimize form listinghttp://forge.typo3.org/issues/897612019-11-24T12:15:43ZMathias Brodalambrodala@pagemachine.de
<p>Currently forms are retrieved as follows in exactly this order:</p>
<ol>
<li>Traverse all configured storage folders</li>
<li>Collect all <code>*.yaml</code> files in a folder</li>
<li>Read the full content of each <code>*.yaml</code> file</li>
<li>Determine if the content looks like a form definition</li>
<li>Skip anything which does not end with <code>.form.yaml</code></li>
</ol>
<p>There is clearly room to improve on each step and especially the order could be changed to have simple filters (like for <code>.form.yaml</code>) executed early using custom FAL filters.</p> TYPO3 Core - Epic #89759 (New): Performance improvements in Forms modulehttp://forge.typo3.org/issues/897592019-11-24T12:08:23ZMathias Brodalambrodala@pagemachine.deTYPO3 Core - Epic #89731 (New): Configuration streamlininghttp://forge.typo3.org/issues/897312019-11-21T18:55:56ZMathias Brodalambrodala@pagemachine.deTYPO3 Core - Task #88220 (Accepted): Documentation for "Allow multiple recipients in EmailFinisher"http://forge.typo3.org/issues/882202019-04-26T12:35:22ZMathias Brodalambrodala@pagemachine.de
<p>The EXT:form documentation (setup/YAML) must be updated for <a class="issue tracker-2 status-5 priority-4 priority-default closed" title="Feature: Allow multiple recipients in EmailFinisher (Closed)" href="http://forge.typo3.org/issues/80420">#80420</a>.</p> TYPO3 Core - Task #86916 (Closed): Use button group for Create/Filter buttons above page treehttp://forge.typo3.org/issues/869162018-11-13T11:54:37ZMathias Brodalambrodala@pagemachine.de
<p>Since the buttons for <em>Create new pages</em> and filtering are mutually exclusive they behave like a <a href="https://getbootstrap.com/docs/3.3/components/#btn-groups" class="external">button group</a>. Thus they should be styled as such:</p>
<p><img src="http://forge.typo3.org/attachments/download/33920/button-group.png" alt="" loading="lazy" /></p> TYPO3 Core - Task #85619 (Closed): Streamline package interdependencieshttp://forge.typo3.org/issues/856192018-07-23T14:39:12ZMathias Brodalambrodala@pagemachine.de
<p>Currently a lot of <code>typo3/cms-*</code> packages have hidden dependencies on other <code>typo3/cms-*</code> packages, e.g. by using views and wizards defined in these packages. For example the <em>Redirects</em> module (<code>typo3/cms-redirects</code>) fails with an exception if <code>typo3/cms-recordlist</code> is not installed.</p>
<p>It should be checked where dependencies are still missing and should be declared explicitly in each Composer manifest.</p> TYPO3 Core - Task #85031 (Closed): Use ServerRequestInterface in ImportExportControllerhttp://forge.typo3.org/issues/850312018-05-17T11:12:52ZMathias Brodalambrodala@pagemachine.deTYPO3 Core - Task #84630 (Closed): Sort list of Composer dependencieshttp://forge.typo3.org/issues/846302018-04-05T16:58:21ZMathias Brodalambrodala@pagemachine.de
<p>Composer has an option to <a href="https://getcomposer.org/doc/06-config.md#sort-packages" class="external">sort packages</a> which makes for a predictable list of dependencies. This should be used.</p> TYPO3 Core - Task #84361 (Closed): Use modal-based new content element wizard everywherehttp://forge.typo3.org/issues/843612018-03-16T17:06:33ZMathias Brodalambrodala@pagemachine.de
<p>There is a modal-based wizard for creating new content elements accessible from the new record view (<em>Click here for wizard!</em>).</p>
<p>This can also be enabled for the list module through some PageTS option.</p>
<p>Instead of hiding this superior UI behind some unknown option this wizard should be enabled everywhere and the option should be removed. Afterwards some code can be deprecated and eventually removed.</p> TYPO3 Core - Task #83417 (Closed): Cannot click label to activate checkbox in Internet Explorer &...http://forge.typo3.org/issues/834172017-12-22T17:45:12ZMathias Brodalambrodala@pagemachine.de
<p>Checkbox fields of the form extension cannot be activated by clicking on their label in Internet Explorer and Edge.</p>
<p>This is a <a href="https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/11345957/" class="external">known and confirmed issue</a></p>
<p>Background for the bug:</p>
<p>The <a href="https://www.w3.org/TR/html51/sec-forms.html#element-attrdef-label-for" class="external">specs for the <code>for</code> attribute</a> say:</p>
<blockquote>
<p>If the for attribute is not specified, but the label element has a labelable element descendant, then the first such descendant in tree order is the label element’s labeled control.</p>
</blockquote>
<p>The definition of a <a href="https://www.w3.org/TR/html51/sec-forms.html#labelable-element" class="external">labelable element</a> is:</p>
<blockquote>
<p>... <input> (if the type attribute is not in the hidden state) ...</p>
</blockquote>
<p>Internet Explorer and Edge ignore this and see the hidden input added to every checkbox field in Fluid forms as element to aim at.</p> TYPO3 Core - Task #77708 (Closed): Follow semverhttp://forge.typo3.org/issues/777082016-08-31T10:35:39ZMathias Brodalambrodala@pagemachine.de
<p>The TYPO3 development/release cycle could be changed to follow <a href="http://semver.org/" class="external">semver</a></p>
<p>This would mean reliable release versions with 100% guarantee of no breaking changes in patch and minor releases. Currently breaking changes also go into minor releases up until the next LTS.</p> TYPO3 Core - Task #69837 (Closed): Extract JavaScript code from SelectSingleBoxElement renderinghttp://forge.typo3.org/issues/698372015-09-15T17:04:44ZMathias Brodalambrodala@pagemachine.de
<p>The embedded JavaScript code within <code>SelectSingleBoxElement</code> should be extracted to a RequireJS module.</p>