Bug 300690

Summary: REGRESSION (iOS 26): Wrong caret position for input field inside a fixed position parent
Product: WebKit Reporter: levihsmn
Component: Layout and RenderingAssignee: Nobody <webkit-unassigned>
Status: RESOLVED DUPLICATE    
Severity: Normal CC: ap, bfulgham, simon.fraser, zalan
Priority: P1    
Version: Safari 26   
Hardware: All   
OS: iOS 26   
Attachments:
Description Flags
Screenshot none

levihsmn
Reported 2025-10-14 04:52:44 PDT
Created attachment 477069 [details] Screenshot Like in 2017 (https://bugs.webkit.org/show_bug.cgi?id=176896) We are experiencing the wrong caret position for an input field inside a fixed position parent. After scrolling a bit down and opening the fixed modal with an input field on it, the text caret finds itself floating below the input. The issue happens on all iOS devices from iOS 26 or upwards. On iOS 18 devices it is working properly.
Attachments
Screenshot (132.88 KB, image/png)
2025-10-14 04:52 PDT, levihsmn 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Alexey Proskuryakov
Comment 1 2025-10-15 10:46:45 PDT
Thank you for the report. Could you please provide a test case? I don't think that this is actionable based on screenshot alone.
levihsmn
Comment 2 2025-10-17 00:23:39 PDT
(In reply to Alexey Proskuryakov from comment #1) > Thank you for the report. Could you please provide a test case? I don't > think that this is actionable based on screenshot alone. Just create a fixed container (like a modal or bottom sheet) and place an input inside. The content behind it must be scrollable. Scroll a bit down and then open the modal.
Alexey Proskuryakov
Comment 3 2025-10-17 08:27:34 PDT
This is not actionable without a test case. It is very unlikely that anyone else will get to creating a test case based on a high level description.
Simon Fraser (smfr)
Comment 4 2025-10-17 09:57:42 PDT
Reopening to dup.
Simon Fraser (smfr)
Comment 5 2025-10-17 09:57:47 PDT
*** This bug has been marked as a duplicate of bug 300952 ***
Note You need to log in before you can comment on or make changes to this bug.