[PAGES-105] Page editing not possible in Firefox Created: 17/Oct/16  Updated: 25/Nov/16  Resolved: 25/Nov/16

Status: Closed
Project: Magnolia pages module
Component/s: None
Affects Version/s: 5.4.9
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Jeffrey van der Heide Assignee: Unassigned
Resolution: Not an issue Votes: 0
Labels: admincentral, admininterface, firefox, page-editor, pages
Remaining Estimate: 2d 1h
Time Spent: 2d 7h
Original Estimate: 5d
Environment:

Firefox 49.0.1 on Windows 7 Enterprise (latest updates installed).


Attachments: PNG File FF-50-win7.png     PNG File Firefox 49.0.1 @ Windows 7.png    
Issue Links:
Relates
relates to MAGNOLIA-5854 Page editing not possible in Firefox ... Open
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:
Story Points: 8

 Description   

Can not edit pages in the pages app.
There's no visible content in the sidebar.
(The items are in the DOM but are not visible.)

Possibly relates to: https://jira.magnolia-cms.com/browse/MAGNOLIA-5854, although that issue is from 2014.



 Comments   
Comment by Oanh Thai Hoang [ 14/Nov/16 ]

It seams that when you press the touch simulator in responsive design view, then the dom.w3c_touch_events.enabled is turned to 1 (enable touch event for FF desktop).

Here is work around solution:

  • Go to about:config
  • Filter the settings to dom.w3c_touch_events.enabled
  • Make sure that the settings are 0 and false (like in the pic). You can refer to another guide for more detail
Comment by Federico Grilli [ 24/Nov/16 ]

For the records, the issue doesn't occur on Win7+ FF 50.0 + Magnolia 5.5

Comment by Jan Haderka [ 25/Nov/16 ]

In summary: Problem doesn't occur with latest FireFox (and with latest Magnolia, tho that is probably irrelevant here). For all the other FF versions, there's known workaround (described above) that can be configured and used by the users of affected versions of FF.

Generated at Mon Feb 12 06:15:41 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.