Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Windows] (Compatibility) Backspace in Edge deletes diacritics + base together #1254

Closed
mcdurdin opened this issue Oct 10, 2018 · 8 comments
Closed

Comments

@mcdurdin
Copy link
Member

@mcdurdin mcdurdin commented Oct 10, 2018

Edge deletes diacritics and base characters together in some scripts (tested so far with Khmer). For example, with khmer_angkor keyboard, typing xjmEr gives ខ្មែរ and five backspaces should delete it all. But in Edge, only 3 backspaces deletes it all, and not in the expected groupings either:

Start with ខ្មែរ.
Bksp: ខ្មែ
Bksp: ខ្
Bksp: empty string

See also:

@mcdurdin
Copy link
Member Author

@mcdurdin mcdurdin commented Oct 28, 2018

@mcdurdin
Copy link
Member Author

@mcdurdin mcdurdin commented Dec 4, 2018

This appears to have been resolved as of Windows 10 build 18290.rs_prerelease.181121-1501 (insider fast ring).

@mcdurdin
Copy link
Member Author

@mcdurdin mcdurdin commented Dec 4, 2018

This appears to have been resolved as of Windows 10 build 18290.rs_prerelease.181121-1501 (insider fast ring).

Hmm. No it hasn't. Sorry about that.

@mcdurdin
Copy link
Member Author

@mcdurdin mcdurdin commented Apr 18, 2019

New Chromium-based Edge does not have this problem. Can close this once that hits release and distribution is wide enough.

@darcywong00
Copy link
Contributor

@darcywong00 darcywong00 commented Oct 15, 2019

Another user reports this compatibility issue with Edge (and Windows 10 Start menu search bar)

When I type into the Edge search bar (or the Windows 10 Start menu search bar, for that matter) using the Rvwangu7 keyboard, I see this:
edge

What I typed was "rvwàng kàí èruò we nø." Similarly, with the SIL Myanmar 3 Keyboard, I get only Roman letters.

Configuration

Keyman 11.0.1361.0 Desktop
Windows 10, Version 1903
Microsoft Edge (version not provided)

@mcdurdin
Copy link
Member Author

@mcdurdin mcdurdin commented Oct 20, 2019

@darcywong00 I wonder if that is a separate issue of Keyman not being activated for Modern UI contexts. Capturing a debug log may be sufficient to tell us if that is the issue (we'd see errors from Modern UI app in the log instead of the expected load of the keyboard). It may well be the ALL APPLICATION PACKAGES permission on %ProgramData%\Keyman` folder, which should be (Read & Execute, List folder contents and Read).

@mcdurdin
Copy link
Member Author

@mcdurdin mcdurdin commented Oct 20, 2019

@darcywong00 see also #1680 and related links.

@mcdurdin
Copy link
Member Author

@mcdurdin mcdurdin commented Jan 18, 2020

Closing this as new Chromium-based Edge has been released and legacy Edge will no longer receive updates.

@mcdurdin mcdurdin closed this Jan 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants