RESOLVED DUPLICATE of bug 297591298323
related to -297591 
https://bugs.webkit.org/show_bug.cgi?id=298323
Summary related to -297591
Neetu
Reported 2025-09-03 09:12:12 PDT
Creating the new ticket for further conversation: What I understood from the previous bug(https://bugs.webkit.org/show_bug.cgi?id=297591)/conversation: The fix for the WebKit regression (slow UI updates due to large CSS selectors) was committed in WebKit revision 299018@main. The fix has not yet shipped in Safari 18.6 (released July 29, 2025). It is included in Safari Technology Preview 218, which is available for macOS Sequoia and Sonoma. The next stable Safari version that may include this fix is Safari 26, currently in beta as of August 5, 2025. Could you please confirm when the fix for this issue will be available in a stable Safari release so, I can inform the team accordingly? Would it be possible for us to provide a temporary solution on our end? Could you please suggest any feasible options? All APIs are experiencing significant delays while loading the page, each taking approximately 24 seconds. As a result, the page fails to load properly. Could you please look into this or suggest any possible optimizations or temporary workarounds? bharath.panyadahundi@dentsplysirona.com manoj.pammina@dentsplysirona.com Is there any way for us to debug this issue or check the logs? Can we investigate it further to propose a solution, since we haven’t been able to identify the root cause yet. We already tried blocking the API calls that were causing delays, but it didn’t have any impact on the speed. or Is there any way we can optimize or improve the CSS selectors to enhance styling performance? Please suggest.
Attachments
Add attachment proposed patch, testcase, etc.
Alexey Proskuryakov
Comment 1 2025-09-03 09:33:12 PDT
WebKit Bugzilla is not an appropriate place for general discussions, we only use it to track bugs and enhancement requests. Please see <https://webkit.org/getting-started/#staying-in-touch> for the other avenues. WebKit developers are unlikely to be able to provide detailed workarounds. Given the nature of the issue, using a smaller list of CSS rules should help. *** This bug has been marked as a duplicate of bug 297591 ***
Note You need to log in before you can comment on or make changes to this bug.