Uploaded image for project: 'Magnolia pages module'
  1. Magnolia pages module
  2. PAGES-126

Magnolia Pages App editing capabilities lost on latest Firefox 52 / Chrome 57 on hybrid devices

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Blocker
    • Resolution: Fixed
    • Affects Version/s: 5.4.7
    • Fix Version/s: 5.5.4
    • Component/s: None
    • Environment:
      Various users on Windows 7 & Windows 10 using the following browser versions (working fine on Macs):

      Chrome: 57.0.2987.110 (64-bit) / 56.0.2924.87/ 56.0.2924.87 (64-bit)
      FireFox: Version 52 doesn’t work on any Windows computer
    • Release notes required:
      Yes
    • Sprint:
      Basel 88, Basel 89, Basel 90
    • Story Points:
      8
    • Magnolia Release:
      5.5.4

      Description

      Multiple clients have reported in parallel that after their web browsers were updated over the past week or so Magnolia page editing functionality was lost.

      Such users are on Windows and on latest Firefox 52 and Chrome 57 and using Magnolia 5.3.5 or 5.4.7 pro STK (and 5.5.2 demoauthor as mentioned below).

      They cannot see the action bar (as per screenshots below). For others, they could see the action bar but could not select actual page areas/components to edit.

      We performed such tests on clean bundles of 5.3.5 and 5.4.7 pro STK which are the two standard versions we implement/support with our clients.


      Unfortunately even testing on Magnolia's demo author (currently on 5.5.2) it doesn't work (https://demoauthor.magnolia-cms.com) - on one browser it doesn't load the action bar, on the other it loads it but you cannot edit page areas.


      Investigation and possible solution:
      The issue had been originally reported on Windows (with touch support) but can be reproduced on any hybrid device supporting both touch screen and mouse support. It has manifested on latest chrome and FF probably due to the fact that since their latest release those browsers support Touch Events API automatically, whereas in prior releases it was disabled by default.

      The issue can actually be reproduced (simulated) e.g. on a MacBook Pro by

      • chrome: opening a tab chrome://flags and enabling Touch Events API
      • FF: opening a tab about:config and setting dom.w3c_touch_events.enabled=1 (0=automatic, 2=disabled)

      The solution consists in enabling mouse selection listener even when touch support is enabled cause that is the case for hybrid devices.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                fgrilli Federico Grilli
                Reporter:
                fwasi Fadi Wissa
              • Votes:
                1 Vote for this issue
                Watchers:
                7 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Date of First Response:

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0d
                  0d
                  Logged:
                  Time Spent - 5d
                  5d