RESOLVED FIXED Bug 233755
Enable NavigationPreloadManager by default 
https://bugs.webkit.org/show_bug.cgi?id=233755
Summary Enable NavigationPreloadManager by default
youenn fablet
Reported 2021-12-02 01:42:12 PST
Enable NavigationPreloadManager by default
Attachments
Patch (1.27 KB, patch)
2021-12-02 01:43 PST, youenn fablet 		no flags
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
youenn fablet
Comment 1 2021-12-02 01:43:33 PST
Created attachment 445692 [details] Patch
Radar WebKit Bug Importer
Comment 2 2021-12-03 05:14:05 PST
<rdar://problem/86014395>
Chris Dumez
Comment 3 2021-12-03 07:21:24 PST
Comment on attachment 445692 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=445692&action=review > Source/WTF/Scripts/Preferences/WebPreferencesExperimental.yaml:1268 > + default: true I am curious, what is the purpose to turn it on in WebCore? Why doesn't turning it on for WebKit suffice?
youenn fablet
Comment 4 2021-12-05 23:49:19 PST
Comment on attachment 445692 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=445692&action=review >> Source/WTF/Scripts/Preferences/WebPreferencesExperimental.yaml:1268 >> + default: true > > I am curious, what is the purpose to turn it on in WebCore? Why doesn't turning it on for WebKit suffice? It is not needed but it seems the default WebCore value should be aligned with the default WebCore user, a.k.a. WebKit.
EWS
Comment 5 2021-12-06 00:13:12 PST
Committed r286540 (244872@main): <https://commits.webkit.org/244872@main> All reviewed patches have been landed. Closing bug and clearing flags on attachment 445692 [details].
Note You need to log in before you can comment on or make changes to this bug.