Bug 38266 - Context menu closes in Chrome on certain Windows 8.1 tablets
Context menu closes in Chrome on certain Windows 8.1 tablets
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: UMC - LDAP directory
UCS 4.0
Other Linux
: P5 enhancement (vote)
: UCS 4.1-x
Assigned To: UMC maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2015-04-14 23:51 CEST by Kevin Dominik Korte
Modified: 2019-01-03 07:17 CET (History)
2 users (show)

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional): Browser compatibility, Mobile devices/tablets
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kevin Dominik Korte univentionstaff 2015-04-14 23:51:36 CEST
When accessing the context menu from a windows 8.1 tablet. (Long press for right click) the context menu closes as soon as the screen isn't pressed anymore, thus it becomes impossible to click on entries of the context menu.
Comment 1 Alexander Kläser univentionstaff 2015-05-29 13:31:33 CEST
We have not tested so far with Windows tablets and officially they are not supported. Did you receive feedback from a client regarding this issue? Does it work by pressing on the little icon on the top right instead?
Comment 2 Kevin Dominik Korte univentionstaff 2015-05-29 18:40:44 CEST
I got the feedback from a client for a Lenovo Thinkpad Helix with full fledged Windows 8.1 (not RT) and Google Chrome. The touchpad is problem free however.
I can reproduce the issue on the HP Stream 7 tablet again 8.1 with Google Chrome both in Modern UI Mode and in Desktop Mode. IE on the HP Stream 7 also works flawless.
I can't reproduce the issue on a Dell Venue 8 Pro Tablet or Dell XPS 13 with neither Chrome nor IE so it might be specific to HP and Lenovo touch screens.

As far as I know, we didn't announce any restriction in the support for device classes for MS Windows 8.1, but I might have overlooked it.
Comment 3 Kevin Dominik Korte univentionstaff 2015-05-29 18:41:59 CEST
(In reply to Kevin Dominik Korte from comment #2)
> IE on the HP Stream 7 also works flawless.
That should be "IE on the HP Stream 7 however works flawless."
Comment 4 Alexander Kläser univentionstaff 2015-06-02 10:32:14 CEST
@Johannes: The adjustments you are currently working also affect the context menu, they might fix this issue.
Comment 5 Alexander Kläser univentionstaff 2015-06-02 10:34:21 CEST
(In reply to Alexander Kläser from comment #4)
> @Johannes: The adjustments you are currently working also affect the context
> menu, they might fix this issue.

@Kevin: Which context menu exactly? LDAP tree navigation or the list context menu? I had the overview page in mind, but this might be wrong as I notice now.
Comment 6 Kevin Dominik Korte univentionstaff 2015-06-25 20:08:57 CEST
(In reply to Alexander Kläser from comment #5)
> @Kevin: Which context menu exactly? LDAP tree navigation or the list context
> menu? I had the overview page in mind, but this might be wrong as I notice
> now.

The customer noticed it and I initially confirmed it on the LDAP Tree. I just tested it again and it basically affects any place where you do a right click.
It most noticeable affects the LDAP Tree navigation, because there are no buttons for editing containers and OUs.

It might be a more generic Dojo Bug for right click or context menus. Is there anyway to produce additional Debug output?
Comment 7 Stefan Gohmann univentionstaff 2019-01-03 07:17:08 CET
This issue has been filled against UCS 4.0. The maintenance with bug and security fixes for UCS 4.0 has ended on 31st of May 2016.

Customers still on UCS 4.0 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.