1. 06 May, 2022 1 commit
    • Benjamin Kott's avatar
      [TASK] Polish SvgTree component styling · 5ecfceb4
      Benjamin Kott authored and Georg Ringer's avatar Georg Ringer committed
      This patch is cleaning up a lot of loose ends in the svg tree component.
      It aims to make the component look more clean and polished.
      
      - Unify focus styling with selected, hover and versioning
      - Ensure the whole node looks focused instead of only some text
      - Replace expand icon to match core icon styling
      - Hide expand icon if page tree is stopped
      - Move trigger to enter stopped pagetree to the front
      - Remove blurry lines for background borders
      - Make the edit input fields use as much space as is available
      - Load common icons always on setup to avoid node refresh on initial loads
      - Reposition the locked icon (another editor is editing)
      - Correct keyboard navigation behaviour and focus setting
      - Keep focus after leaving the edit mode without changes
      - Adjust positioning to rely on calculation instead of hardcoded values
      - Align drag delete target
      - Make drag positions more visible to the user when moving a page
      - Improve styling of tooltips when dragging elements
      - Add border to select tree component to make scroll boundaries visible
      
      Affected Areas:
      - PageTree
      - FileTree
      - SelectTree
      
      Releases: main
      Resolves: #97344
      Change-Id: I6034e0cbc1079b93b24c5c1a99e0299946874b2f
      Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/74203
      
      
      Tested-by: Benjamin Franzke's avatarBenjamin Franzke <bfr@qbus.de>
      Tested-by: core-ci's avatarcore-ci <typo3@b13.com>
      Tested-by: Georg Ringer's avatarGeorg Ringer <georg.ringer@gmail.com>
      Reviewed-by: Benjamin Franzke's avatarBenjamin Franzke <bfr@qbus.de>
      Reviewed-by: Georg Ringer's avatarGeorg Ringer <georg.ringer@gmail.com>
      5ecfceb4
  2. 04 May, 2022 1 commit
  3. 21 Apr, 2022 1 commit
  4. 16 Apr, 2022 1 commit
  5. 12 Apr, 2022 1 commit
  6. 11 Apr, 2022 1 commit
  7. 08 Apr, 2022 2 commits
  8. 07 Apr, 2022 4 commits
  9. 06 Apr, 2022 1 commit
  10. 05 Apr, 2022 3 commits
  11. 01 Apr, 2022 1 commit
    • Oliver Bartsch's avatar
      [FEATURE] Introduce TCA type "color" · 12a6613f
      Oliver Bartsch authored
      In the process of using dedicated TCA types,
      the new TCA type "color" is introduced and
      replaces "renderType=colorpicker" of TCA
      type "input".
      
      Notable changes to the previous behaviour:
      
      - The maxlength is set to 7, since this is
        the maximum length for the hex color
        (#XXXXX | /#[0-9a-fA-F]{3,6}/)
      - The only allowed eval is "null"
      - "trim" is always done in DataHandler and FormEngine
      
      Note: The maxlength might change again
      as soon as we switch to another color
      picker which supports e.g. opacity
      specification.
      
      The TCA type is now wrapped into a custom
      element. Also does it now use the general
      ValuePicker JS module, instead of duplicating
      this functionality in the ColorPicker JS module.
      
      The ColorPicker JS module is furthermore
      refactored. Global initialization of the
      color pickers is deprecated. To initialize
      the ColorPicker for an element, it has to
      be provided as first argument in the
      initialize() method.
      
      used command:
      > composer u typo3/cms-styleguide
      
      Resolves: #97271
      Releases: main
      Change-Id: I1418b100ae214499be7b01f6c94539a6cb6baa3b
      Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/74121
      
      
      Tested-by: Stefan Bürk's avatarStefan Bürk <stefan@buerk.tech>
      Tested-by: core-ci's avatarcore-ci <typo3@b13.com>
      Tested-by: Benni Mack's avatarBenni Mack <benni@typo3.org>
      Tested-by: Oliver Bartsch's avatarOliver Bartsch <bo@cedev.de>
      Reviewed-by: Stefan Bürk's avatarStefan Bürk <stefan@buerk.tech>
      Reviewed-by: Benni Mack's avatarBenni Mack <benni@typo3.org>
      Reviewed-by: Oliver Bartsch's avatarOliver Bartsch <bo@cedev.de>
      12a6613f
  12. 30 Mar, 2022 1 commit
  13. 29 Mar, 2022 1 commit
  14. 28 Mar, 2022 4 commits
  15. 26 Mar, 2022 1 commit
  16. 25 Mar, 2022 1 commit
  17. 22 Mar, 2022 2 commits
  18. 14 Mar, 2022 2 commits
    • Oliver Bartsch's avatar
      [FEATURE] Introduce TCA type "link" · 40d4f901
      Oliver Bartsch authored
      In our process of using dedicated TCA types,
      the new TCA type "link" is introduced and
      replaces "renderType=link" of TCA type "input".
      
      Notable changes to the previous "inputLink" behaviour:
      
      - "linkPopup" fieldControl is now always used by the
        FormEngine element
      - Corresponding fieldControl options are migrated
        to columns config
      - The type now makes use of include lists instead of
        exclude lists
      - The allowed link types are now evaluated in DataHandler
      - "trim" is always done in DataHandler and FormEngine
      - "max" is no longer evaluated
      - "softref=typolink" is automatically set
      
      As mentioned, the TCA type "link" uses include lists.
      This also required to adjust the LinkPopup fieldControl,
      as well as the Link Browser classes. The previously
      used "blinkLink[Fields|Options]" options are still
      supported in case the "LinkPopup" fieldControl is used
      for another TCA type. However, they might be deprecated
      soon.
      
      Finally, the TSconfig key for the MailLinkHandler is
      renamed from "mail" to "email", to unify the naming
      in the codebase.
      
      Resolves: #97159
      Releases: main
      Change-Id: Ied9e957b973ed8904736e5d4353a989ea76065d8
      Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/73866
      
      
      Tested-by: core-ci's avatarcore-ci <typo3@b13.com>
      Tested-by: Benni Mack's avatarBenni Mack <benni@typo3.org>
      Tested-by: Susanne Moog's avatarSusanne Moog <look@susi.dev>
      Tested-by: Oliver Bartsch's avatarOliver Bartsch <bo@cedev.de>
      Reviewed-by: Benni Mack's avatarBenni Mack <benni@typo3.org>
      Reviewed-by: Susanne Moog's avatarSusanne Moog <look@susi.dev>
      Reviewed-by: Oliver Bartsch's avatarOliver Bartsch <bo@cedev.de>
      40d4f901
    • Benni Mack's avatar
      [BUGFIX] Use sys_history for workspaces stage changes + comments · c6342a66
      Benni Mack authored
      Historically, a stage change
      (publishing or "editing => ready to publish") has been
      tracked - along with the comment in sys_log with the
      action=6 (update) and details_nr=30, where then the logs
      are read again for the workspaces module.
      
      Reading from sys_log is a problem as this data is
      very volatile (there is even a scheduler task to delete
      old sys_log entries older than e.g. 90 days, so we loose
      comments).
      
      This change now stores the information inside the
      sys_history table about a stage change, so the history
      of such an action is preserved, along with the comment.
      
      The workspaces module now reads from sys_history (via
      RecordHistory class) and from sys_log if there are
      still old comments.
      
      The reading from sys_log can then be removed at a later
      change.
      
      Resolves: #97158
      Releases: main, 11.5
      Change-Id: I055b944462f57a889681a6a236c329af29bb8d80
      Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/73861
      
      
      Tested-by: Susanne Moog's avatarSusanne Moog <look@susi.dev>
      Tested-by: core-ci's avatarcore-ci <typo3@b13.com>
      Tested-by: Oliver Bartsch's avatarOliver Bartsch <bo@cedev.de>
      Tested-by: Benni Mack's avatarBenni Mack <benni@typo3.org>
      Reviewed-by: Susanne Moog's avatarSusanne Moog <look@susi.dev>
      Reviewed-by: Oliver Bartsch's avatarOliver Bartsch <bo@cedev.de>
      Reviewed-by: Benni Mack's avatarBenni Mack <benni@typo3.org>
      c6342a66
  19. 07 Mar, 2022 1 commit
  20. 27 Feb, 2022 1 commit
  21. 25 Feb, 2022 1 commit
  22. 24 Feb, 2022 1 commit
  23. 21 Feb, 2022 1 commit
  24. 20 Feb, 2022 1 commit
  25. 18 Feb, 2022 3 commits
  26. 17 Feb, 2022 1 commit
  27. 16 Feb, 2022 1 commit