Bug 245539

Summary:	Office.com becomes practically unusable on iPad (and maybe other devices)
Product:	WebKit	Reporter:	nadav.bar.lev <nadav.bar.lev>
Component:	Page Loading	Assignee:	Nobody <webkit-unassigned>
Status:	RESOLVED CONFIGURATION CHANGED
Severity:	Major	CC:	ahmad.saleem792, ap, beidson, karlcow, webkit-bug-importer, zalan
Priority:	P2	Keywords:	BrowserCompat, InRadar
Version:	Other
Hardware:	iPhone / iPad
OS:	iOS 15

Description nadav.bar.lev 2022-09-22 14:08:37 PDT

### Steps to reproduce
Browse to Office.com
Login with a Microsoft account
Click on Word/Excel/PowerPoint
Repeat step 3 for 4-5 times
The page becomes unresponsive and the UI freezes for a decent amount of seconds

### Expected behavior
As per my comparison to other browsers, Google Chrome and Microsoft Edge (both Chromium based browsers) are able to render this webpage perfectly fine, providing the smooth and expected user experience I expected WKWebView to provide.

### Actual behavior
The page becomes laggy, freezes the UI for a few seconds and makes the use of Office.com practically impossible.

### Device & build information
Device: iPad Air (3rd Generation) / Simulator - iPad 9th Generation
Build version: 105 / Local build of main at 613707d

Comment 1 Alexey Proskuryakov 2022-09-23 19:11:08 PDT

Thank you for the report! Could you please clarify the scenario?

- Are you observing this with your own WebKit build in iOS Simulator? How are you building and running Safari for this?
- What is "105 / Local build of main at 613707d"? 613707d is not a hash in the WebKit repository AFAICT.
- Can you reproduce with stock WebKit?

Comment 2 Radar WebKit Bug Importer 2022-09-29 14:09:17 PDT

<rdar://problem/100581281>

Comment 3 Ahmad Saleem 2023-09-26 17:36:28 PDT

@Alan - you did recent fix around office.com, do you think this bug is still applicable or fixed?

Comment 4 zalan 2023-09-26 18:21:01 PDT

(In reply to Ahmad Saleem from comment #3)
> @Alan - you did recent fix around office.com, do you think this bug is still
> applicable or fixed?
Good point, I think it's fixed now (268148@main)