[MGNLUI-3678] No component edit bars (Chrome, hybrid touch device) Created: 26/Nov/15  Updated: 28/Mar/17  Resolved: 26/Mar/17

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: 5.4.3
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Ruth Stocks Assignee: Unassigned
Resolution: Duplicate Votes: 2
Labels: chrome, hybrid, touch
Remaining Estimate: 0d
Time Spent: 1.5h
Original Estimate: Not Specified
Environment:

Windows 10
Chrome Version 46.0.2490.86 m


Issue Links:
Relates
relates to MGNLUI-3832 Page Editor iframe sized incorrectly ... Closed
causality
duplicate
duplicates PAGES-126 Magnolia Pages App editing capabiliti... Closed
is duplicated by MGNLUI-3693 Research why mouse isn't working on a... Closed
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:

 Description   

Pages are not editable in Chrome Version 46.0.2490.86 m. The area bars display, but are unresponsive - the component bars do not display when clicking the area bars.



 Comments   
Comment by Ruth Stocks [ 30/Nov/15 ]

Tested on https://demoauthor.magnolia-cms.com/ and local magnolia-enterprise-pro-demo-bundle-5.4.3-tomcat-bundle

Comment by Bret Lederle [ 03/Nov/16 ]

Has any progress made on this? I am still experiencing it with Chrome Version 54.0.2840.87 m and Magnolia 5.4.9. Here are some other behaviors I have noticed.

  • Works with Chrome on OSX 10.11.6
  • Works with Responsive mode from "Device Toolbar" (Ctrl-Shift-M)
Comment by Mikaël Geljić [ 07/Feb/17 ]

Out of curiosity, could you blederle and ruths indicate:

  • whether your Windows devices have touch support?
  • whether it's the only interaction which is unresponsive? e.g. trying to click through the app launcher, pulse, favorites, and a typical content app?

Thanks for you help!

Comment by Bret Lederle [ 07/Feb/17 ]

whether your Windows devices have touch support? Yes! I had not thought of this being an issue since I don't use my touchscreen often. I am able to open components by touching the bar on my touchscreen. Still an issue to be fixed, but this somewhat explains the behavior.

whether it's the only interaction which is unresponsive? e.g. trying to click through the app launcher, pulse, favorites, and a typical content app? I have not seen any Chrome issues with any of these components. Favorites is the only feature I don't use often. The only additional issue I've noticed is not being able to scroll down on a page that extends beyond the bottom of the screen. Even trying to do this action with my touchscreen today did not work. And it is working well on Firefox.

Comment by Ruth Stocks [ 08/Feb/17 ]
  • My computer does have touch support and I can access the edit bars by touching the screen.
  • Everything else I tested (app launcher, favorites, apps etc. ) seems to be fine, i.e. works with a mouse click.
Comment by Mikaël Geljić [ 08/Feb/17 ]

Thanks you two for confirming, I adjusted the issue title to reflect that. Meanwhile this is yet to prioritize.

Generated at Mon Feb 12 09:09:02 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.