Blue box moved up by one pixel, red is showing. An example: http://build.webkit.sed.hu/results/x86-64%20Linux%20Qt%20Release%20WebKit2%20%28Pixel%20Tests%29/r151642%20%284731%29/css2.1/20110323/absolute-non-replaced-height-002-diffs.html css2.1/20110323/absolute-non-replaced-height-002.htm css2.1/20110323/absolute-non-replaced-width-001.htm css2.1/20110323/absolute-non-replaced-width-002.htm css2.1/20110323/absolute-non-replaced-width-003.htm css2.1/20110323/absolute-non-replaced-width-004.htm css2.1/20110323/absolute-non-replaced-width-005.htm css2.1/20110323/absolute-non-replaced-width-006.htm css2.1/20110323/absolute-non-replaced-width-007.htm css2.1/20110323/absolute-non-replaced-width-008.htm css2.1/20110323/absolute-non-replaced-width-009.htm css2.1/20110323/absolute-non-replaced-width-010.htm css2.1/20110323/absolute-non-replaced-width-011.htm css2.1/20110323/absolute-non-replaced-width-012.htm css2.1/20110323/absolute-non-replaced-width-013.htm css2.1/20110323/absolute-non-replaced-width-014.htm css2.1/20110323/absolute-non-replaced-width-016.htm css2.1/20110323/inline-block-non-replaced-width-001.htm css2.1/20110323/inline-block-non-replaced-width-002.htm Box moved by one pixel. Example: http://build.webkit.sed.hu/results/x86-64%20Linux%20Qt%20Release%20WebKit2%20%28Pixel%20Tests%29/r151642%20%284731%29/css2.1/t0803-c5505-mrgn-01-e-a-diffs.html css2.1/20110323/block-non-replaced-height-005.htm css2.1/20110323/block-non-replaced-height-006.htm css2.1/20110323/block-non-replaced-width-007.htm css2.1/20110323/block-replaced-width-001.htm css2.1/20110323/float-non-replaced-width-006.htm
I have been unable to reproduce this with WK1 and Qt 5.1. I will test with WK2 tomorrow.
I am not able to reproduce the issue with Qt 5.1 and WK2 either. Many blocks move a pixel due to difference between fonts with aliasing and without, but none show any red or other error.
=== Bulk closing of Qt bugs === If you believe that this bug report is still relevant for a non-Qt port of webkit.org, please re-open it and remove [Qt] from the summary. If you believe that this is still an important QtWebKit bug, please fill a new report at https://bugreports.qt-project.org and add a link to this issue. See http://qt-project.org/wiki/ReportingBugsInQt for additional guidelines.