New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 796351 link

Starred by 2 users
Status: Untriaged
Owner: ----
Cc:
█ krajshree@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 3
Type: Feature



Sign in to add a comment

Not able to catch character accent menu event on Mac

Reported by chrisli...@gmail.com, Dec 19 2017 
Chrome Version       : 63.0
URLs (if applicable) :
OS version               : Sierra Version 10.12.6

What steps will reproduce the problem?
(1) On an input box, hold a key down until its alternate characters are displayed. 
(2) Select one of character to input that alternate character.

What is the expected result?
Should be able to prevent the character accent menu by setting the attribution of the input element.
Should be able to check whether the character accent menu is displayed.
Should be able to tell if a input/onchange/keydown/keypress/keyup event is triggered by using the character accent menu.

What happens instead?
The browser gets no information about the character accent menu.

Comment 1 by krajshree@chromium.org, Dec 20 2017

Cc: krajshree@chromium.org
Components: Blink>Input
Labels: Needs-Triage-M63 Triaged-ET Needs-Feedback
chrisli615@ - Thanks for filing the issue...!!

Could you please provide a sample webpage/test file to test the issue from TE-end.
This will help us in triaging the issue further.

Thanks...!!

Comment 2 by c...@ixl.com, Dec 20 2017 

https://jsfiddle.net/chrisli615/en62kbo0/

There is no way to prevent the character accent menu, and there is no way to check whether an event is triggered by the accent menu either.
example.png
305 KB View Download

Comment 3 by dtapu...@chromium.org, Jan 4 2018 

This sounds like a feature request not a bug. This behaves the same way in Safari as Chrome does. Have you opened a bug against Safari? What has been their response?

Comment 4 by chrisli...@gmail.com, Jan 8 2018 

I have logged a bug for Safari as well, but they hasn't responded yet.

I logged it as bug because it is causing problem when I am listening on the keydown. For example, when I am listen on the keydown for arrow key, there is actually no way for me to determine whether the keydown is on the character menu or on the input element. I was wondering if that is something can be caught on the browser side.

If this should be logged as a feature request, could you please help me update it?
Project Member

Comment 5 by sheriffbot@chromium.org, Jan 8 2018

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "krajshree@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 6 by dtapu...@chromium.org, Jan 11 2018

Labels: -Type-Bug Type-Feature
Status: Available (was: Unconfirmed)
We need to do some feasibility analysis on whether we can prevent the IME dialog.
Project Member

Comment 7 by sheriffbot@chromium.org, Jan 14

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
►

Sign in to add a comment