Skip to content
Snippets Groups Projects
  1. Jun 13, 2024
  2. Jun 12, 2024
  3. Jun 11, 2024
  4. Jun 10, 2024
  5. Jun 06, 2024
  6. Jun 04, 2024
  7. Jun 03, 2024
    • Imko Schumacher's avatar
      [BUGFIX] Fix initialization of 00:00 time input · 39b6e51b
      Imko Schumacher authored
      The value of the `time` input is sent as an ISO date to the
      FormEngine, except for the time "00:00", which is just submitted
      as "0".
      
      This has lead to the input field not getting populated by
      the JavaScript initialization, and the input "00:00" was lost.
      
      In cases where such a `time` input is set as a required
      field, the validation would then fail because of the field
      getting interpreted as being empty/unset.
      
      With this patch, a "0" value is also interpreted as a valid
      "1970-01-01T00:00:00+00:00" string, that is parseable by
      FormEngine. Note this only affects display within the
      FormEngine; the format of the stored data is not changed
      (converted by DataHandler to proper values and covered by
      existing tests).
      
      IMPORTANT: This only applies to NULLABLE time|timesec
      inputs. Only for this configuration it is possible to
      decide, that a stored "0" value in the database is
      actually "00:00" and not an unset entry.
      
      Integrators/developers need to set 'nullable'
      TCA key to 'true' of the corresponding 'config' array,
      in case they want to make a time/timesec input picker
      be able to store and retrieve "00:00" as a valid
      timestamp.
      
      Resolves: #102602
      Releases: main, 12.4
      Change-Id: Id5dae6564a5da9ab3abd99bdc14b718cc7064464
      Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84459
      
      
      Tested-by: default avatarBenjamin Franzke <ben@bnf.dev>
      Reviewed-by: default avatarBenjamin Franzke <ben@bnf.dev>
      Tested-by: default avatarcore-ci <typo3@b13.com>
      39b6e51b
  8. May 31, 2024
  9. May 29, 2024
  10. May 27, 2024
  11. May 26, 2024
  12. May 25, 2024
  13. May 24, 2024
  14. May 21, 2024
  15. May 14, 2024
  16. May 13, 2024
    • Benjamin Franzke's avatar
      [BUGFIX] Make CE actions clickable after edit or visibility toggle · 1dc8d2e6
      Benjamin Franzke authored
      When a content element (CE) gets edited or the visibility is toggled,
      the page module is reloaded with an anchor in the URL to scroll to the
      content element that was updated.
      
      After #103381 it was not possible anymore to click the "+ Content"
      button above such CE. The reason is that a pseudo element
      `:target:before` is generated with a specific height and margin to
      overcome the height of the floating module docheader, overlaying the
      CE action button.
      In the patch mentioned before, `overflow: hidden` was removed to make
      the `box-shadow` of the CE visible, finally causing this bug.
      
      To solve this issue the pseudo element add it #97036 is replaced by the
      CSS option scroll-padding-top. It incorperates the maximum docheader
      size plus a slight margin that is slightly lower than the grid margin –
      but not equal to – to move shadows of adjacent elements out of sight.
      
      Resolves: #103672
      Related: #103381
      Related: #97036
      Releases: main, 12.4
      Change-Id: I8d5c9eadd45e5507e39b1fb728de65d31c1d6689
      Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/84234
      
      
      Reviewed-by: default avatarBenjamin Franzke <ben@bnf.dev>
      Tested-by: default avatarcore-ci <typo3@b13.com>
      Tested-by: default avatarBenjamin Franzke <ben@bnf.dev>
      1dc8d2e6
  17. May 03, 2024
  18. May 02, 2024
  19. Apr 30, 2024