Uploaded image for project: 'XWiki Platform'
  1. XWiki Platform
  2. XWIKI-20129

'Minor Edit' and 'Autosave' checkboxes are not displayed in the right place for a short time when editing Home page in-place

    XMLWordPrintable

Details

    • Bug
    • Resolution: Unresolved
    • Minor
    • None
    • 13.10.5, 14.7, 14.4.4
    • None
    • None
    • Windows 11 Pro 64 bit, Edge 105, using a local instance of XWiki 14.4.4 on PostgreSQL 14, Tomcat 9.0.65
    • Unknown

    Description

      STEPS TO REPRODUCE

      1. Open an XWiki 14.4.4 instance, login with an Advanced user (optional, but I've noticed that it can help to reproduce more often for some reason)
      2. Go to Home page
      3. Edit it in WYSIWYG mode and click "Save & View"
      4. Edit it in-place right after that
      5. Observe the 'Minor Edit' and 'Autosave' checkboxes placement at the bottom of editing area

      EXPECTED RESULTS

      The 'Minor Edit' and 'Autosave' have regular font and are placed in-line with "Save & View", "Save", "Cancel" and "Add Summary" field.

      ACTUAL RESULTS

      The 'Minor Edit' and 'Autosave' are displayed in Bold and "Autosave" is displayed under "Save & View", "Save" and "Cancel" buttons.

      What I've noticed is that after a short time (10-15 secs), they are displayed back at the right place.

      Sometimes the issue does not occur using the above steps, sometimes reproduces just by editing the page in-place twice, one right after another edit or just edit the page in WYSIWYG mode and just click 'Cancel', then edit it in-place.

      In browser's console there are the following errors (not sure if they are related though):

      The service worker navigation preload request was cancelled before 'preloadResponse' settled. If you intend to use 'preloadResponse', use waitUntil() or respondWith() to wait for the promise to settle.

      and

      Uncaught (in promise) DOMException: The service worker navigation preload request was cancelled before 'preloadResponse' settled. If you intend to use 'preloadResponse', use waitUntil() or respondWith() to wait for the promise to settle.

      The issue was reproduced only on Edge 105 apparently (also tested on Chrome 105 and Firefox 104) and it reproduced also on XWiki 13.10.5.

      Attachments

        Activity

          People

            Unassigned Unassigned
            iandriuta Ilie Andriuta
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: