Changes between Version 12 and Version 13 of QtWebKit/CodeCamp200912

Timestamp:

Dec 14, 2009, 11:10:28 AM (15 years ago)

Author:

carol.szabo@nokia.com

Comment:

--

QtWebKit/CodeCamp200912

@@ -31 +31 @@
  * Holger is MIA in the morning... claimed to be sick
  * BenjaminP and Noam look into QtWebKit's CSS Animation speed and see we have a clip region with 800 rects... A quick test shows a nice improvement.
- * Holger talks with Zoltan of Szeged about performance tuning. Both find out that current focus is more on performance and that both parties more or less see the same in oprofile reports. CSS and JS parsing is dominating our page loading. Szeged's idea is to try a hand written parser for comparisoon. Some more coordination is needed, for the next few months there is no overlap in work though.
+ * Holger talks with Zoltan of Szeged about performance tuning. Both find out that current focus is more on performance and that both parties more or less see the same in profile reports. CSS and JS parsing is dominating our page loading. Szeged's idea is to try a hand written parser for comparison. Some more coordination is needed, for the next few months there is no overlap in work though.
 
 === User Interface ===
+
+1st Day
+ * Discussed interfacing of touch events with WebKit.
+
+2nd Day
+
+Form controls issues:
+ * Multiple selection list box has too small items in order to be selectable on a touch device. Different platforms and devices have specialized controls that allow comfortable user interaction. Currently WebKit does not allow usage of such controls. Multiple selection list box shall instantiate the appropriate QtControl upon focus. (Carol Szabo, cszabo1)
+      * Determine the appropriate control.
+ * There are websites that show simulated popup menus upon hovering over a link, but clicking on the link takes the user to a new page. The desired user experience for a touch device is that generally touching focusable controls results in an emulated mouse click, but for links as described above the first touch should result only in hovering, only the second touch should result in a click.
+      * Support hover without click on touch (Misha Tyutyunik).
+ * WAP CSS can specify restrictions to acceptable characters in an edit box. This could be useful in assigning actions to keypresses on devices with limited keyboards. I.e. if an edit control only accepts numeric keyboard should act as a numeric only keyboard, versus having the first key press result in letters being generated. (Carol Szabo, cszabo1)
+ * Find closest focusable node to point (Joe Ligman)
+ * List focusable nodes that intersect a given rectangle. (Joe Ligman)
+ * Ability to select items from a simulated dropdown list while an edit box has the focus. (Misha Tyutyunik)
+      * Solution 1: Change the way the editbox is exited to not exit on down if the JavaScript handles the down key and makes changes to the document.
+      * Solution 2: Change the editbox to exit only on long page down if there is a handler for the key in JavaScript or another solution for releaving the down key from the exit edit box action if needed.
+ * Adding the ability to scroll WebElements (Joe Ligman)
+ * Having the virtual keyboard send key events to WebCore. (Joe Ligman)
+ * Adding recursive scrolling to QWebFrame. (Joe Ligman)
+ * Styling of Form Controls (Carol Szabo, cszabo1)
+
+3rd Day
+
+ * No activity for this group.
 
 === Java Script Core ===