WebKit Bugzilla
New
Browse
Log In
×
Sign in with GitHub
or
Remember my login
Create Account
·
Forgot Password
Forgotten password account recovery
NEW
281162
REGRESSION (iOS 18): Removed DOM elements still visible
https://bugs.webkit.org/show_bug.cgi?id=281162
Summary
REGRESSION (iOS 18): Removed DOM elements still visible
Robin Jakobsson
Reported
2024-10-09 13:38:53 PDT
Created
attachment 472886
[details]
Video comparing iOS 18 and iOS 17.5 I've experienced a regression in iOS 18 with some DOM elements still being visible after they've been removed from the DOM tree. In the example video, our calendar event "laban" should only be visible on "Torsdag". Sorry about the very specific example, I'm not sure how to begin to recreate this behaviour as I haven't seen it in any web browser before.
Attachments
Video comparing iOS 18 and iOS 17.5
(32.22 MB, video/quicktime)
2024-10-09 13:38 PDT
,
Robin Jakobsson
no flags
Details
View All
Add attachment
proposed patch, testcase, etc.
Alexey Proskuryakov
Comment 1
2024-10-09 17:43:08 PDT
Thank you for the report! Would you be willing to share whether this affects any live websites or shipping apps?
Radar WebKit Bug Importer
Comment 2
2024-10-09 17:43:21 PDT
<
rdar://problem/137639028
>
Robin Jakobsson
Comment 3
2024-10-09 22:40:54 PDT
It does impact a live website and an app which uses that website. I can give a testable environment with a one-time password, to the person(s) would like to see it or inspect it live.
Karl Dubost
Comment 4
2024-10-11 06:27:40 PDT
The website
https://business.itswavy.com/
requires a login. Robin indeed without an access we can't really do anything. Except if you manage to create a reduced test case. What is the behavior on Android?
Robin Jakobsson
Comment 5
2024-11-15 00:18:58 PST
I got around the issue by applying the CSS-property: will-change: transform; to the containing element. It stopped the rendering issue from occurring. I'll try to make an reproducible example.
Note
You need to
log in
before you can comment on or make changes to this bug.
Top of Page
Format For Printing
XML
Clone This Bug