RESOLVED FIXED 165289
[iOS] Add a WebView private configuration for changing the WebContent update frequency
https://bugs.webkit.org/show_bug.cgi?id=165289
Summary [iOS] Add a WebView private configuration for changing the WebContent update ...
Said Abou-Hallawa
Reported 2016-12-01 16:45:14 PST
We need a expose a preference which allows us to control the fps of web content updates.
Attachments
Patch (5.50 KB, patch)
2016-12-01 18:00 PST, Said Abou-Hallawa
no flags
Patch (8.00 KB, patch)
2016-12-02 17:29 PST, Said Abou-Hallawa
no flags
Patch (7.88 KB, patch)
2016-12-02 18:19 PST, Said Abou-Hallawa
no flags
Patch (8.16 KB, patch)
2016-12-02 18:55 PST, Said Abou-Hallawa
no flags
Said Abou-Hallawa
Comment 1 2016-12-01 18:00:47 PST
Tim Horton
Comment 2 2016-12-01 18:06:01 PST
Comment on attachment 295919 [details] Patch I think this should be a private WKWebViewConfiguration parameter instead. It's set-once, and shouldn't be adjustable by apps.
Jon Lee
Comment 3 2016-12-01 19:17:25 PST
Said Abou-Hallawa
Comment 4 2016-12-02 17:29:56 PST
Tim Horton
Comment 5 2016-12-02 17:35:17 PST
Comment on attachment 296029 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=296029&action=review > Source/WebKit2/UIProcess/API/APIPageConfiguration.h:122 > + uint32_t m_contentUpdateFrequency = 0; modern style would be uint32_t m_contentUpdateFrequency { 0 } > Source/WebKit2/UIProcess/API/Cocoa/WKWebViewConfiguration.mm:480 > +- (NSNumber *)_contentUpdateFrequency Why is this still NSNumber? NSUInteger or unsigned or something, no need for the boxing. > Source/WebKit2/UIProcess/mac/RemoteLayerTreeDrawingAreaProxy.mm:139 > +uint32_t RemoteLayerTreeDrawingAreaProxy::contentUpdateFrequency() const Isn't this code compiled on Mac?
Said Abou-Hallawa
Comment 6 2016-12-02 18:19:38 PST
Said Abou-Hallawa
Comment 7 2016-12-02 18:25:54 PST
Comment on attachment 296029 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=296029&action=review >> Source/WebKit2/UIProcess/API/APIPageConfiguration.h:122 >> + uint32_t m_contentUpdateFrequency = 0; > > modern style would be uint32_t m_contentUpdateFrequency { 0 } Fixed. >> Source/WebKit2/UIProcess/API/Cocoa/WKWebViewConfiguration.mm:480 >> +- (NSNumber *)_contentUpdateFrequency > > Why is this still NSNumber? NSUInteger or unsigned or something, no need for the boxing. I changed it to NSUInteger. >> Source/WebKit2/UIProcess/mac/RemoteLayerTreeDrawingAreaProxy.mm:139 >> +uint32_t RemoteLayerTreeDrawingAreaProxy::contentUpdateFrequency() const > > Isn't this code compiled on Mac? Yes, you are right. I kept the function but I make it return a 0 for Mac. This is to avoid adding if the header file and WKOneShotDisplayLinkHandler initWithDrawingAreaProxy function.
Tim Horton
Comment 8 2016-12-02 18:29:24 PST
(In reply to comment #7) > Comment on attachment 296029 [details] > Patch > > View in context: > https://bugs.webkit.org/attachment.cgi?id=296029&action=review > > >> Source/WebKit2/UIProcess/API/APIPageConfiguration.h:122 > >> + uint32_t m_contentUpdateFrequency = 0; > > > > modern style would be uint32_t m_contentUpdateFrequency { 0 } > > Fixed. > > >> Source/WebKit2/UIProcess/API/Cocoa/WKWebViewConfiguration.mm:480 > >> +- (NSNumber *)_contentUpdateFrequency > > > > Why is this still NSNumber? NSUInteger or unsigned or something, no need for the boxing. > > I changed it to NSUInteger. OK. > >> Source/WebKit2/UIProcess/mac/RemoteLayerTreeDrawingAreaProxy.mm:139 > >> +uint32_t RemoteLayerTreeDrawingAreaProxy::contentUpdateFrequency() const > > > > Isn't this code compiled on Mac? > > Yes, you are right. I kept the function but I make it return a 0 for Mac. > This is to avoid adding if the header file and WKOneShotDisplayLinkHandler > initWithDrawingAreaProxy function. WKOneShotDisplayLinkHandler is already #if'd
Said Abou-Hallawa
Comment 9 2016-12-02 18:55:53 PST
WebKit Commit Bot
Comment 10 2016-12-02 19:59:19 PST
Comment on attachment 296032 [details] Patch Clearing flags on attachment: 296032 Committed r209294: <http://trac.webkit.org/changeset/209294>
WebKit Commit Bot
Comment 11 2016-12-02 19:59:22 PST
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.