and enable it by default for qt wk2.
Created attachment 127959 [details] Patch
Comment on attachment 127959 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=127959&action=review > Source/WebKit2/ChangeLog:3 > + Add frame flattening setting to QWebPreferences. You could add a [WK2] prefix before landing :) > Source/WebKit/qt/declarative/qdeclarativewebview_p.h:316 > + Q_PROPERTY(bool frameFlatteningEnabled READ frameFlatteningEnabled WRITE setFrameFlatteningEnabled) Hm, are you sure about adding the property to the QML1 webview? If yes, then the property needs to have a version. (See revision stuff in qdeclarativewebview)
(In reply to comment #2) > (From update of attachment 127959 [details]) > View in context: https://bugs.webkit.org/attachment.cgi?id=127959&action=review > > > Source/WebKit2/ChangeLog:3 > > + Add frame flattening setting to QWebPreferences. > > You could add a [WK2] prefix before landing :) > > > Source/WebKit/qt/declarative/qdeclarativewebview_p.h:316 > > + Q_PROPERTY(bool frameFlatteningEnabled READ frameFlatteningEnabled WRITE setFrameFlatteningEnabled) > > Hm, are you sure about adding the property to the QML1 webview? If yes, then the property needs to have a version. (See revision stuff in qdeclarativewebview) I thought having WebKit and WK2 APIs synced up wouldn't be such a bad idea, but I dont have a strong preference on it.
(In reply to comment #3) > (In reply to comment #2) > > (From update of attachment 127959 [details] [details]) > > View in context: https://bugs.webkit.org/attachment.cgi?id=127959&action=review > > > > > Source/WebKit2/ChangeLog:3 > > > + Add frame flattening setting to QWebPreferences. > > > > You could add a [WK2] prefix before landing :) > > > > > Source/WebKit/qt/declarative/qdeclarativewebview_p.h:316 > > > + Q_PROPERTY(bool frameFlatteningEnabled READ frameFlatteningEnabled WRITE setFrameFlatteningEnabled) > > > > Hm, are you sure about adding the property to the QML1 webview? If yes, then the property needs to have a version. (See revision stuff in qdeclarativewebview) > > I thought having WebKit and WK2 APIs synced up wouldn't be such a bad idea, but I dont have a strong preference on it. I suggest we keep the QML1 API untouched, as we're not actively using it.
Comment on attachment 127959 [details] Patch new patch is coming up.
Created attachment 128157 [details] Patch
Comment on attachment 128157 [details] Patch r=me, but we have to be careful to not use it when WebKit is used on platforms like Windows or Mac OS, where browser show scrollbars.
Comment on attachment 128157 [details] Patch Clearing flags on attachment: 128157 Committed r108471: <http://trac.webkit.org/changeset/108471>
All reviewed patches have been landed. Closing bug.