Investigate Private Browsing mode for IME
Categories
(Core :: Widget: Win32, enhancement, P4)
Tracking
()
Tracking | Status | |
---|---|---|
firefox49 | --- | affected |
People
(Reporter: m_kato, Unassigned)
References
()
Details
(Keywords: inputmethod, Whiteboard: tpi:+)
Attachments
(1 file)
3.39 KB,
patch
|
Details | Diff | Splinter Review |
Reporter | ||
Updated•9 years ago
|
Reporter | ||
Comment 1•9 years ago
|
||
![]() |
||
Updated•9 years ago
|
Reporter | ||
Comment 2•8 years ago
|
||
Reporter | ||
Comment 3•8 years ago
|
||
Comment 4•6 years ago
|
||
Just FYI, Microsoft Edge team sent a patch to Chromium team to specify IS_PRIVATE InputScope when incognito mode is enabled.
https://chromium-review.googlesource.com/c/chromium/src/+/1591886
So there is a chance that a recent or future version of MS-IME starts respecting IS_PRIVATE to enable their private mode. I really hope MS-IME team isn't limiting this behavior to Chromium-based browsers.
Reporter | ||
Comment 5•6 years ago
|
||
(In reply to Yohei Yukawa from comment #4)
Just FYI, Microsoft Edge team sent a patch to Chromium team to specify IS_PRIVATE InputScope when incognito mode is enabled.
https://chromium-review.googlesource.com/c/chromium/src/+/1591886
So there is a chance that a recent or future version of MS-IME starts respecting IS_PRIVATE to enable their private mode. I really hope MS-IME team isn't limiting this behavior to Chromium-based browsers.
Nice!. Thanks for information.
Reporter | ||
Updated•6 years ago
|
Reporter | ||
Comment 6•6 years ago
|
||
Microsoft IME on Windows 10 20H1 will support IS_PRIVATE input scope. I don't know it for Windows 10 19H2. Moving to bug 1549394 to fix this.
Description
•