EFL and Qt will use this preferences.
Created attachment 184185 [details] Patch
Created attachment 184192 [details] Patch
Comment on attachment 184185 [details] Patch This doesn't actually expose the preference to API and you also have not explained what this would be used for and why it is necessary.
(In reply to comment #3) > (From update of attachment 184185 [details]) > This doesn't actually expose the preference to API and you also have not explained what this would be used for and why it is necessary. It is very reasonable concern. I did block Bug 105978 that uses this preference, but I did not explain enough. sorry for that. EFL and Qt want to use page scale in WebCore as Chromium did. So EFL and Qt want to set applyDeviceScaleFactorInCompositor and applyPageScaleFactorInCompositor as Chromium did. EFL and Qt want to set both in UI Process, so we need to add new API in WebPreferencesStore although we don't add new API in WK2 API (WKPreferences). (I made a mistake about title.) Could we add new those APIs in WebPreferencesStore?
Created attachment 184399 [details] Patch
(In reply to comment #3) > (From update of attachment 184185 [details]) > This doesn't actually expose the preference to API and you also have not explained what this would be used for and why it is necessary. I think the point is that it is not a user preference, but something which should be set by out view. Dongsung, is there a reason why this cannot always be set in the WebProcess, like together with turning on fixed layouting?
(In reply to comment #6) > (In reply to comment #3) > > (From update of attachment 184185 [details] [details]) > > This doesn't actually expose the preference to API and you also have not explained what this would be used for and why it is necessary. > > I think the point is that it is not a user preference, but something which should be set by out view. Dongsung, is there a reason why this cannot always be set in the WebProcess, like together with turning on fixed layouting? aha, do you mean it is fine that setting them in WebPage::setUseFixedLayout(bool fixed)? I did not do that because I did not fully understand what is FixedLayout. Ok, I see. This bug is invalid. Thank kenneth and sam.