- 04 Jan, 2021 1 commit
-
-
With Bootstrap 5, <select> fields make use of the class `form-select`. This patch aims to replace every occurrence of `form-control` used with select fields. Since Bootstrap finally brings proper styling for select boxes, the custom implementation rendering chevrons can be removed. In the same run, the `input-$size` classes are migrated to its new class names and some obsolete classes have been removed. Resolves: #93135 Releases: master Change-Id: I0044127cc380bddfbaec0b9f730123959f7288bd Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/67247 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Martin Kutschker <mkutschker-typo3@yahoo.com> Tested-by:
Benjamin Franzke <bfr@qbus.de> Reviewed-by:
-
- 20 Dec, 2020 1 commit
-
-
This changes removes the frontend framework Bootstrap 3, and adds Bootstrap 5 beta 1 (we expect Bootstrap 5 final by the time we release TYPO3 v11 LTS). Bootstrap v3 is not supported by the Bootstrap team any longer, so an update is critical for TYPO3 Core. Bootstrap v5 adds a few accessibility improvements as well as flexbox for rendering containers and grids throughout TYPO3 Backend. All JS components are not bound to jQuery anymore, and have been reworked. A lot of HTML/CSS changes happened, which we slowly migrate (and not in a huge change) to TYPO3's templates, in order to keep this change managable. A legacy CSS/SCSS file is added to keep some backwards-compatibility classes to ease the migration for extension developers who have built their own backend modules. Key features of Bootstrap 5: * "rem" instead of "px" is used by default * CSS variables are introduced * Improved bootstrap focus outline styling (buttons / inputs / links) * Simplified grid functionality * use new button color mixin to increase contrast: Primary, Success and Warning Button color is now dark instead of white EXT:styleguide was used as a basis for upgrading to keep compatibility as much as possible, but more changes will be coming in the next few minor releases. Resolves: #92616 Releases: master Change-Id: Iec989f39649b5460b055ec879199faf38e424f2b Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/66247 Tested-by:
Oliver Hader <oliver.hader@typo3.org> Tested-by:
Oliver Bartsch <bo@cedev.de>
Tested-by: Benni Mack <benni@typo3.org> Reviewed-by:
Oliver Bartsch <bo@cedev.de>
Reviewed-by:
-
- 16 Apr, 2020 1 commit
-
-
This change aims to reduce the amount of inline JavaScript by removing `onchange` events. * extracts inline JavaScript from templates * introduces `TYPO3/CMS/Backend/GlobalEventHandler` module * adjusts PHP type-hints to their correct & actual values Resolves: #91052 Releases: master Change-Id: If92391bd48f89df57fbb0ed6f8b0936da0e1a49d Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64191 Tested-by:
-
- 03 Dec, 2019 1 commit
-
-
Simplify the UI of the toolbar by hiding the select field if there is only one option to choose from which doesn't make sense. Resolves: #89829 Releases: master Change-Id: I6e58aae1bab25777bca21f058524e447f569d73a Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/62517 Tested-by:
Markus Klein <markus.klein@typo3.org> Tested-by:
Joerg Kummer <typo3@enobe.de> Reviewed-by:
-
- 23 Apr, 2019 1 commit
-
-
The indentations in the HTML templates are out of control. Even if we provide an EditorConfig, which should ensure that the files are all uniformly indented. There seems to have been an increasing aversion to TABS over time. This has led to the fact that above all newly created templates have always been indented with SPACES instead of TABS. We now have a mix of TABS and SPACES in our project, partly also in a single file. To avoid this in the future, all existing templates were converted to indentations with SPACES and the provided EditorConfig was adapted. In order to really, really make sure that it doesn't get out of hand, we also introduce a new linter, which ensures that all HTML templates are properly indented. Resolves: #88180 Releases: master Change-Id: I86d23120bc68e3696f398b1ae76f1efc4804d501 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/60522 Tested-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Tested-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Reviewed-by:
Oliver Wand <wand@itaw.de> Reviewed-by:
Oliver Klee <typo3-coding@oliverklee.de> Reviewed-by:
Helmut Hummel <typo3@helhum.io> Reviewed-by:
-
- 23 Feb, 2018 1 commit
-
-
Add data attributes in backend toolbar and backend menu components, to have general identifier for binding guided tours popover and more features that can be based on this. Resolves: #80500 Releases: master, 8.7 Change-Id: I2add8b8c28ecd37967b7b23f71392aa71f209da5 Reviewed-on: https://review.typo3.org/52197 Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Mathias Schreiber <mathias.schreiber@typo3.com> Tested-by:
Frank Naegler <frank.naegler@typo3.org> Tested-by:
-
- 03 Oct, 2015 1 commit
-
-
A new class structure around "ModuleTemplate" is introduced to substitute the rusty "DocumentTemplate". The architecture can be seen as wrapper around the main html content a backend controller action creates. ModuleTemplate provides an API especially for the "doc header" and unifies its display and creation. The patch releases single controller actions from fiddling with doc header details like actual button HTML and hands over this concern to the framework, so it can steer these parts at a central place. Since this API and its embedding in the framework is a rather complex task that will require further tweaks, this main API is mostly marked as "experimental" for now: It will further settle with 8. For extension authors it means that *if* this API is used, there may be code adaptions required in version 8 since parts of the API will be adapted to further needs. Resolves: #69814 Releases: master Change-Id: I81cb9f01ebc4b13d8d88a928811e563d83ec97cd Reviewed-on: http://review.typo3.org/43465 Reviewed-by:
Benjamin Kott <info@bk2k.info> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Tested-by:
Mathias Schreiber <mathias.schreiber@wmdb.de> Tested-by:
-
