[magnolia-dev] [JIRA] (PAGES-126) Magnolia Pages App editing capabilities lost on latest Firefox 52 / Chrome 57 on hybrid devices

[on behalf of Michael Mühlebach]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Mühlebach updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia pages module /  PAGES-126  
 
 
  Magnolia Pages App editing capabilities lost on latest Firefox 52 / Chrome 57 on hybrid devices   
 

  
 
 
 
 

 
Change By: 
 Michael Mühlebach  
 
 
Sprint: 
 Basel 88, Basel 89 , Basel 90  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (PAGES-126) Magnolia Pages App editing capabilities lost on latest Firefox 52 / Chrome 57 on hybrid devices

[on behalf of Michael Mühlebach]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Mühlebach updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia pages module /  PAGES-126  
 
 
  Magnolia Pages App editing capabilities lost on latest Firefox 52 / Chrome 57 on hybrid devices   
 

  
 
 
 
 

 
Change By: 
 Michael Mühlebach  
 
 
Story Points: 
 5 8  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (PAGES-126) Magnolia Pages App editing capabilities lost on latest Firefox 52 / Chrome 57 on hybrid devices

[JIRA (on behalf of Federico Grilli)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Federico Grilli updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia pages module /  PAGES-126  
 
 
  Magnolia Pages App editing capabilities lost on latest Firefox 52 / Chrome 57 on hybrid devices   
 

  
 
 
 
 

 
Change By: 
 Federico Grilli  
 
 
Labels: 
 blocked  browser_issue chrome firefox page-editor pages-app  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (PAGES-126) Magnolia Pages App editing capabilities lost on latest Firefox 52 / Chrome 57 on hybrid devices

[JIRA (on behalf of Federico Grilli)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Federico Grilli updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia pages module /  PAGES-126  
 
 
  Magnolia Pages App editing capabilities lost on latest Firefox 52 / Chrome 57 on hybrid devices   
 

  
 
 
 
 

 
Change By: 
 Federico Grilli  
 
 
Labels: 
 blocked browser_issue chrome firefox page-editor pages-app  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (PAGES-126) Magnolia Pages App editing capabilities lost on latest Firefox 52 / Chrome 57 on hybrid devices

[JIRA (on behalf of Federico Grilli)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Federico Grilli updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia pages module /  PAGES-126  
 
 
  Magnolia Pages App editing capabilities lost on latest Firefox 52 / Chrome 57 on hybrid devices   
 

  
 
 
 
 

 
Change By: 
 Federico Grilli  
 
 
Comment: 
 Parked as it can be merged only to 5.4.x branch. 5.5.x needs to wait after 5.5.3 release.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (PAGES-126) Magnolia Pages App editing capabilities lost on latest Firefox 52 / Chrome 57 on hybrid devices

[JIRA (on behalf of Federico Grilli)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Federico Grilli updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia pages module /  PAGES-126  
 
 
  Magnolia Pages App editing capabilities lost on latest Firefox 52 / Chrome 57 on hybrid devices   
 

  
 
 
 
 

 
Change By: 
 Federico Grilli  
 
 
Labels: 
 blocked  browser_issue chrome firefox page-editor pages-app  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (PAGES-126) Magnolia Pages App editing capabilities lost on latest Firefox 52 / Chrome 57 on hybrid devices

[JIRA (on behalf of Federico Grilli)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Federico Grilli updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia pages module /  PAGES-126  
 
 
  Magnolia Pages App editing capabilities lost on latest Firefox 52 / Chrome 57 on hybrid devices   
 

  
 
 
 
 

 
Change By: 
 Federico Grilli  
 
 
Fix Version/s: 
 5.4.11  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (PAGES-126) Magnolia Pages App editing capabilities lost on latest Firefox 52 / Chrome 57 on hybrid devices

[JIRA (on behalf of Federico Grilli)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Federico Grilli updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia pages module /  PAGES-126  
 
 
  Magnolia Pages App editing capabilities lost on latest Firefox 52 / Chrome 57 on hybrid devices   
 

  
 
 
 
 

 
Change By: 
 Federico Grilli  
 
 
Labels: 
 browser_issue chrome firefox page-editor pages-app  parked  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (PAGES-126) Magnolia Pages App editing capabilities lost on latest Firefox 52 / Chrome 57 on hybrid devices

[JIRA (on behalf of Federico Grilli)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Federico Grilli updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia pages module /  PAGES-126  
 
 
  Magnolia Pages App editing capabilities lost on latest Firefox 52 / Chrome 57 on hybrid devices   
 

  
 
 
 
 

 
Change By: 
 Federico Grilli  
 
 
Fix Version/s: 
 5.5.4  
 
 
Fix Version/s: 
 5.4.11  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (PAGES-126) Magnolia Pages App editing capabilities lost on latest Firefox 52 / Chrome 57 on hybrid devices

[on behalf of Michael Mühlebach]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Mühlebach updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia pages module /  PAGES-126  
 
 
  Magnolia Pages App editing capabilities lost on latest Firefox 52 / Chrome 57 on hybrid devices   
 

  
 
 
 
 

 
Change By: 
 Michael Mühlebach  
 
 
Story Points: 
 3 5  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (PAGES-126) Magnolia Pages App editing capabilities lost on latest Firefox 52 / Chrome 57 on hybrid devices

[on behalf of Michael Mühlebach]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Mühlebach updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia pages module /  PAGES-126  
 
 
  Magnolia Pages App editing capabilities lost on latest Firefox 52 / Chrome 57 on hybrid devices   
 

  
 
 
 
 

 
Change By: 
 Michael Mühlebach  
 
 
Sprint: 
 Basel 88 , Basel 89  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (PAGES-126) Magnolia Pages App editing capabilities lost on latest Firefox 52 / Chrome 57 on hybrid devices

[JIRA (on behalf of Federico Grilli)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Federico Grilli updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia pages module /  PAGES-126  
 
 
  Magnolia Pages App editing capabilities lost on latest Firefox 52 / Chrome 57 on hybrid devices   
 

  
 
 
 
 

 
Change By: 
 Federico Grilli  
 

  
 
 
 
 

 
 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. !image-2017-03-17-23-43-04-309.png|thumbnail!  !image-2017-03-17-23-42-33-316.png|thumbnail! 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. !broken on demo author as well.png|thumbnail! *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= disabled automatic , 2= automatic disabled )The solution consists in enabling mouse selection listener even when touch support is enabled cause that is the case for hybrid devices.  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 
   

[magnolia-dev] [JIRA] (PAGES-126) Magnolia Pages App editing capabilities lost on latest Firefox 52 / Chrome 57 on hybrid devices

[JIRA (on behalf of Federico Grilli)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Federico Grilli updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia pages module /  PAGES-126  
 
 
  Magnolia Pages App editing capabilities lost on latest Firefox 52 / Chrome 57 on hybrid devices   
 

  
 
 
 
 

 
Change By: 
 Federico Grilli  
 

  
 
 
 
 

 
 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. !image-2017-03-17-23-43-04-309.png|thumbnail!  !image-2017-03-17-23-42-33-316.png|thumbnail! 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. !broken on demo author as well.png|thumbnail! *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=disabled,2=automatic)The solution consists in enabling mouse selection listener even when touch support is enabled cause that is the case for hybrid devices  (like some Windows10 laptops where the issue occurred) .  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  

[magnolia-dev] [JIRA] (PAGES-126) Magnolia Pages App editing capabilities lost on latest Firefox 52 / Chrome 57 on hybrid devices

[JIRA (on behalf of Federico Grilli)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Federico Grilli updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia pages module /  PAGES-126  
 
 
  Magnolia Pages App editing capabilities lost on latest Firefox 52 / Chrome 57 on hybrid devices   
 

  
 
 
 
 

 
Change By: 
 Federico Grilli  
 
 
Release notes required: 
 Yes  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: 

[magnolia-dev] [JIRA] (PAGES-126) Magnolia Pages App editing capabilities lost on latest Firefox 52 / Chrome 57 on hybrid devices

[JIRA (on behalf of Federico Grilli)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Federico Grilli updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia pages module /  PAGES-126  
 
 
  Magnolia Pages App editing capabilities lost on latest Firefox 52 / Chrome 57 on hybrid devices   
 

  
 
 
 
 

 
Change By: 
 Federico Grilli  
 

  
 
 
 
 

 
 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. !image-2017-03-17-23-43-04-309.png|thumbnail!  !image-2017-03-17-23-42-33-316.png|thumbnail! 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. !broken on demo author as well.png|thumbnail! *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  be  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=disabled,2=automatic)The solution consists in enabling mouse selection listener even when touch support is enabled cause that is the case for hybrid devices (like some Windows10 laptops where the issue occurred).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

[magnolia-dev] [JIRA] (PAGES-126) Magnolia Pages App editing capabilities lost on latest Firefox 52 / Chrome 57 on hybrid devices

[JIRA (on behalf of Federico Grilli)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Federico Grilli updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia pages module /  PAGES-126  
 
 
  Magnolia Pages App editing capabilities lost on latest Firefox 52 / Chrome 57 on hybrid devices   
 

  
 
 
 
 

 
Change By: 
 Federico Grilli  
 

  
 
 
 
 

 
 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. !image-2017-03-17-23-43-04-309.png|thumbnail!  !image-2017-03-17-23-42-33-316.png|thumbnail! 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. !broken on demo author as well.png|thumbnail! *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 be 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=disabled,2=automatic) The solution consists in enabling mouse selection listener even when touch support is enabled cause that is the case for hybrid devices (like some Windows10 laptops where the issue occurred).  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  

[magnolia-dev] [JIRA] (PAGES-126) Magnolia Pages App editing capabilities lost on latest Firefox 52 / Chrome 57 on hybrid devices

[JIRA (on behalf of Federico Grilli)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Federico Grilli updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia pages module /  PAGES-126  
 
 
  Magnolia Pages App editing capabilities lost on latest Firefox 52 / Chrome 57 on hybrid devices   
 

  
 
 
 
 

 
Change By: 
 Federico Grilli  
 

  
 
 
 
 

 
 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. !image-2017-03-17-23-43-04-309.png|thumbnail!  !image-2017-03-17-23-42-33-316.png|thumbnail! 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. !broken on demo author as well.png|thumbnail!    *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 be 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=disabled,2=automatic)  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 

[magnolia-dev] [JIRA] (PAGES-126) Magnolia Pages App editing capabilities lost on latest Firefox 52 / Chrome 57 on hybrid devices

[JIRA (on behalf of Federico Grilli)]

Title: Message Title


 
 
 
 

 
 
 

 
   
 Federico Grilli updated an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Magnolia pages module /  PAGES-126  
 
 
  Magnolia Pages App editing capabilities lost on latest Firefox 52 / Chrome 57 on hybrid devices   
 

  
 
 
 
 

 
Change By: 
 Federico Grilli  
 
 
Summary: 
 Magnolia Pages App editing capabilities lost on latest Firefox 52 / Chrome 57 on  Windows  hybrid devices  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian JIRA (v7.2.6#72008-sha1:26175bf)  
 
 

 
   
 

  
 

  
 

   




For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: