Hi Ismail, thanks for investigating this issue and for finding a possible fix.

I can't comment on the specifics, but usually the best way to deal
with issues like this is to file a bug report:

http://webkit.org/quality/reporting.html

The bugs database has a comment feature to allow for back-and-forth
discussion there.  And if this a Qt-specific issue, you can give it a
title that begins "[Qt] ...."  Finally, if you'd like to submit a
formal patch for the issue, you can follow the instructions here:

http://webkit.org/coding/contributing.html

Otherwise, you can simply include your suggested fix below and someone
else can take it from there.