Merge conflict Gerrit cannot merge this change. It needs a rebase onto main.

Review main Work in progress Orphaned

88260[TASK] Use native browser resizing for viewpage module

Benjamin Franzke CR 0 V 0 Normal +38 −118 updated 02/18/25, 13:53

Commit message

Use CSS based native browser resizing (`resize: both`)
instead of the JavaScript based resizable actions from
`interactjs` library, which is a framework of its own
(currently 128K in size).

Commands executed:
  npm remove interactjs
  npm run build

Test this change

Run a command in your clone of the TYPO3 Core. Then try what the change does and vote on Verified in Gerrit. How to review a patch

Check out patch set 3
git fetch https://review.typo3.org/Packages/TYPO3.CMS refs/changes/60/88260/3 && git checkout FETCH_HEAD
Cherry-pick onto main
git fetch https://review.typo3.org/Packages/TYPO3.CMS refs/changes/60/88260/3 && git cherry-pick FETCH_HEAD

Review

  • Code review CR 0 Needs a vote
  • Verified V 0 Needs a vote
    • core-ci +1 CI

Issues 1

Files 11

Review log 69

  1. Benjamin Franzke uploaded patch set 1 02/18/25, 12:17

  2. Benjamin Franzke uploaded patch set 2 02/18/25, 12:18

  3. core-ci voted on patch set 1 V -1 02/18/25, 12:21 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/74311

  4. Benjamin Franzke updated the commit message in patch set 3 02/18/25, 12:23

  5. core-ci voted on patch set 2 V +1 02/18/25, 12:26 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/74312

  6. core-ci voted on patch set 3 V +1 02/18/25, 12:29 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/74313

  7. Andreas Kienast commented on patch set 3 02/18/25, 12:33

    I'm a bit reluctant here. I fully support the removal of interact, however, the usability of the resize handling became worse, IMO. Previously it was possible to change the size by dragging all edges, not I'm forced to drag a tiny corner.
  8. Benjamin Franzke commented on patch set 3 02/18/25, 12:36

    Reply Unresolved

    > usability of the resize handling became worse, IMO I disagree :) It now uses what the user is used to. The browser UI uses the same resize-handles for `<textarea>`. Furthermore I think that a visible resize-drag-element are easier to understand – I could only understand "where" I'm able to resize by reading the code and inspecting the `resize-e` "handles".
  9. Benjamin Franzke marked it work in progress 02/18/25, 13:53