46 lines
1.1 KiB
Markdown
46 lines
1.1 KiB
Markdown
|
## 155: WPF Spell Checking fails in unexpected ways
|
||
|
|
|
||
|
|
### Scope
|
||
|
|
Edge
|
||
|
|
|
||
|
|
### Version Introduced
|
||
|
|
4.6.1
|
||
|
|
|
||
|
|
### Version Reverted
|
||
|
|
4.6.2
|
||
|
|
|
||
|
|
### Source Analyzer Status
|
||
|
|
Not planned
|
||
|
|
|
||
|
|
### Change Description
|
||
|
|
|
||
|
|
This includes a number of WPF Spell Checker issues:
|
||
|
|
- WPF Spell Checker sometimes throws COMException
|
||
|
|
- WPF Spell Checker fails with System.UnauthorizedAccessException when applications are launched using 'run as different user'
|
||
|
|
- WPF Spell Checker incorrectly identifies spelling errors in compound words like 'Hausnummer' in German.
|
||
|
|
|
||
|
|
- [ ] Quirked
|
||
|
|
- [ ] Build-time break
|
||
|
|
|
||
|
|
### Recommended Action
|
||
|
|
|
||
|
|
Issue #1 - This has been fixed in .NET Framework 4.6.2
|
||
|
|
Issue #2 - WPF Spell Checker is no longer supported when applications are launched using 'run as different user'. Starting .NET Framework 4.6.2, applications launched in this manner will no longer crash unexpectedly - instead the Spell Checker will be silently disabled.
|
||
|
|
Issue #3 - This has been fixed in .NET Framework 4.6.2.
|
||
|
|
|
||
|
|
|
||
|
|
### Affected APIs
|
||
|
|
* Not detectable via API analysis
|
||
|
|
|
||
|
|
### Category
|
||
|
|
Windows Presentation Foundation (WPF)
|
||
|
|
|
||
|
|
<!--
|
||
|
|
### Original Bug
|
||
|
|
172504
|
||
|
|
173922
|
||
|
|
180203
|
||
|
|
-->
|
||
|
|
|
||
|
|
|