Activity log for bug #1532903

Date Who What changed Old value New value Message
2016-01-11 18:51:12 Chris Coulson bug added bug
2016-01-11 18:51:54 Chris Coulson oxide: status New Triaged
2016-01-11 18:51:56 Chris Coulson oxide: importance Undecided Medium
2016-01-11 18:53:30 Chris Coulson description WebView.icon has a few limitations that can only really be resolved by offering a replacement to this API: - It provides the remote URL of the icon, requiring the application to use Qt's network stack to download it. Applications need to be careful for icongnito webviews, as the icon download may leave a footprint on disk. - It doesn't allow the application to support touch icons (<link rel="apple-touch-icon">) - It doesn't allow the application to select an appropriate icon when there is more than one. I propose we replace it with something like this: class OxideQQuickWebView { QLIst<OxideQQuickFavicon> icons() const; } class OxideQQuickFavicon { enum Type { TypeIcon, TypeTouch, TypePrecomposedTouch } QUrl imageUrl() const; QUrl resourceUrl() const; Type type() const; QSizeF size() const; } imageUrl() will provide an image: URL that can be passed to Image elements, and Oxide will register an image provider that will handle the image download via Chromium's network stack WebView.icon has a few limitations that can only really be resolved by offering a replacement to this API: - It provides the remote URL of the icon, requiring the application to use Qt's network stack to download it. Applications need to be careful for icongnito webviews, as the icon download may leave a footprint on disk. - It doesn't allow the application to support touch icons (<link rel="apple-touch-icon">) - It doesn't allow the application to select an appropriate icon when there is more than one. I propose we replace it with something like this: class OxideQQuickWebView {   QLIst<OxideQQuickFavicon> icons() const; } class OxideQQuickFavicon {   enum Type {     TypeIcon,     TypeTouch,     TypePrecomposedTouch   }   QUrl imageUrl() const;   QUrl resourceUrl() const;   Type type() const;   QSizeF size() const; } imageUrl() will provide an image: URL that can be passed to Image elements, and Oxide will register an image provider that will handle the image download via Chromium's network stack. The API should probably provide a way to create a QImage too, although that would need to asynchronous.