Closed
Bug 1958516
Opened 26 days ago
Closed 7 days ago
outlook.office.com - Predictive text appears in the wrong spot when typing
Categories
(Web Compatibility :: Site Reports, defect, P2)
Tracking
(Webcompat Priority:P2, Webcompat Score:2, firefox139 fixed)
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
firefox139 | --- | fixed |
People
(Reporter: railioaie, Unassigned)
References
()
Details
(Keywords: webcompat:site-report, Whiteboard: [webcompat-source:web-bugs])
User Story
platform:windows,mac,linux impact:annoyance configuration:general affects:all branch:release diagnosis-team:dom user-impact-score:300
Attachments
(1 file)
582.21 KB,
video/mp4
|
Details |
Environment:
Operating system: Windows 10
Firefox version: Firefox 135.0
Preconditions:
Clean profile
In Outlook "Show suggested replies" and "Suggest words or phrases as I type" from settings should be checked.
Steps to reproduce:
- Navigate to: https://outlook.office.com/mail/
- Create a new email
- Start typing
Expected Behavior:
The suggestions are displayed correctly
Actual Behavior:
The predictive text appears in the wrong spot when typing
Notes:
- Reproduces regardless of the status of ETP
- Reproduces in firefox-release
- Does not reproduce in Chrome, Firefox Beta , Firefox Nightly
Created from https://github.com/webcompat/web-bugs/issues/149161
Updated•25 days ago
|
Webcompat Score: --- → 1
Updated•23 days ago
|
Severity: -- → S4
User Story: (updated)
Webcompat Priority: --- → P2
Webcompat Score: 1 → 6
Keywords: webcompat:needs-diagnosis
Priority: -- → P2
Updated•22 days ago
|
Webcompat Score: 6 → 2
Comment 2•22 days ago
|
||
I can't reproduce this issue in Nightly but can still see this in Release Fx 137.
I ran the mozregression tool and got the fix bug 1951832, which looks reasonable.
Updated•22 days ago
|
Depends on: better-white-space-normalizer
Updated•21 days ago
|
Keywords: webcompat:needs-diagnosis
The issue has been fixed.
Tested with:
Browser / Version: Firefox Nightly 139.0a1 (2025-04-22)
Operating System: Windows 10
Status: NEW → RESOLVED
Closed: 7 days ago
Resolution: --- → FIXED
status-firefox139:
--- → fixed
You need to log in
before you can comment on or make changes to this bug.
Description
•