RESOLVED FIXED 21864
Add userData() and setUserData() methods to QWebHistoryItem.
https://bugs.webkit.org/show_bug.cgi?id=21864
Summary Add userData() and setUserData() methods to QWebHistoryItem.
Yael
Reported Friday, October 24, 2008 9:48:21 PM UTC
Add userData() and setUserData() methods to QWebHistoryItem. Also add signal QWebFrame::aboutToUpdateHistory(QWebHistoryItem*).
Attachments
Add new API (6.55 KB, patch)
2008-10-24 14:32 PDT, Yael
hausmann: review+
Yael
Comment 1 Friday, October 24, 2008 10:32:05 PM UTC
Created attachment 24652 [details] Add new API Add new API.
Darin Adler
Comment 2 Monday, November 3, 2008 5:35:04 PM UTC
Why is this separate from bug 21863? It would be clearer to have a single patch for review than these two patches.
Yael
Comment 3 Monday, November 3, 2008 6:02:07 PM UTC
(In reply to comment #2) > Why is this separate from bug 21863? It would be clearer to have a single patch > for review than these two patches. > Sorry for the confusion. I was told that it is easier to review patches if they are broken into smaller chunks. If that's not the case, I will not break my patches in the future. thanks!
Darin Adler
Comment 4 Monday, November 3, 2008 6:25:38 PM UTC
(In reply to comment #3) > Sorry for the confusion. I was told that it is easier to review patches if they > are broken into smaller chunks. If that's not the case, I will not break my > patches in the future. thanks! That is indeed true in general. But in this case, the chunks don't have any good logical separation -- there's just a lower level machinery that's unused and then adding the API to get at it. Please don't take this as a general push to make patches larger in the future! It's good to break things up into the smallest sensible chunks that you can.
Simon Hausmann
Comment 5 Tuesday, November 4, 2008 4:23:21 PM UTC
Comment on attachment 24652 [details] Add new API Looks good! I'll do a few small cleanups before applying.
Simon Hausmann
Comment 6 Tuesday, November 4, 2008 4:23:41 PM UTC
Landed in r38097
Note You need to log in before you can comment on or make changes to this bug.