This week (3) in QtWebKit trunk

Posted by Simon Hausmann on January 24, 2010 · 4 comments

This week has been a very busy week! Here’s a list of the landed changes that affect the Qt port, in chronological order:

  • Tor Arne has ported the Qt build of DumpRenderTree to run on Windows. (r53526, r53543).
  • Luiz continued with cleaning up the combobox popup handling.(33418).
  • Ben from the Google Team fixed a bug where touch events weren’t sent to iframes (33894).
  • No’am landed support in the Qt bindings that allows passing pixmaps and images as arguments in signals/slots/properties, which can then easily be turned into image elements or data urls. (32461).
  • Benjamin cleaned up the QWebPage autotest (32216).
  • On Thursday we landed No’am’s implementation of GraphicsLayer. This accelerates the composition of layers with animated opacity or transform attributes, through content caching in pixmaps. Layers are mapped to QGraphicsItems with enabled CacheMode and the animation is driven by the Qt Animation Framework.The feature is disabled by default currently as it’s not stable yet, but it’s a fantastic start! (33514).
  • Diego continued implementing missing functions in the Qt DRT (33945).
  • Jakub fixed a crash with video elements and phonon (33842).
  • Girish fixed a bug with combobox popups in transformed QGraphicsWebViews (r53703, 33887).
  • Robert fixed 5 layout tests by fixing support for window.close() and window.closed() in the Qt DRT (32953).
  • Kent fixed bugs with Object.getOwnPropertyDescriptor (33948, 33946).
QShare(this)

Possibly related posts:

  1. This week (9) in QtWebKit trunk

4 comments

1 Peter January 25, 2010 at 9:45 am
 

Could someone please look at this crash bug? https://bugs.webkit.org/show_bug.cgi?id=31765

2 Kensai January 26, 2010 at 10:16 pm
 

It’s good Qt Technology is following so close the Webkit development. Since Webkit is a major force behind browser engine technology, bringing it to Qt is a winning move.

I was wondering: what’s the official stance of Qt Technology for the new WebGL from Khronos? Since it has made it to the Webkit, it might be a great tool for 3D graphics, as Canvas is for 2D.

3 Benjamin January 27, 2010 at 2:14 pm
 

@Peter: Andreas is having a look

@Kensai: We would also like to have WebGL in the Qt port but there is no work being done on it currently. If you want to help on that you are welcome :)

4 STiAT February 1, 2010 at 11:01 am
 

I’m wondering why google is always found in QtWebKit bugfixes. What interest do they have in QtWebKit?

Comments on this entry are closed.

Previous post:

Next post: