Version: 1.2.0 (using KDE 4.7.2) OS: Linux Form feeds should be treated as white space; WebKit ignores them entirely. Reproducible: Always Steps to Reproduce: Tell Konqueror to display attachment 68065 [details]. Actual Results: In HTML, ASCII form feed () is defined as a white space character. Enter "" by typing F7 char 12. Expected Results: In HTML, ASCII form feed ( ) is defined as a white space character. Enter " " by typing F7 char 12.
Few things... #1. With QtWebkit 2.2, I do not see any difference when viewing the attached test case in Konqueror+webkit, Firefox or Chromium. Did you attach the correct test case ? #2. The version of QtWebKit you are testing with, i.e. the one that came with Qt 4.7.x, is very very old. Need to perform the test with QtWebKit >= 2.2 which should come with Qt 4.8. #3. If this issue is confirmed in when tested against QtWebKit >= 2.2, then it needs to be reported upstream[1] against QtWebKit as the matter would be beyond the scope of kwebkitpart. [1] http://trac.webkit.org/wiki/QtWebKitBugs
(In reply to comment #1) > Few things... > > #1. With QtWebkit 2.2, I do not see any difference when viewing the attached > test case in Konqueror+webkit, Firefox or Chromium. Did you attach the correct > test case ? Yes, and Firefox also does it wrong. <URL: http://input.mozilla.com/pl/opinion/2654409 > This is not a big issue because a form feed is usually preceded by a line feed, so the test case is artificial. > > #2. The version of QtWebKit you are testing with, i.e. the one that came with > Qt 4.7.x, is very very old. Need to perform the test with QtWebKit >= 2.2 which > should come with Qt 4.8. Pending then. Although I am afraid by the time it will be distributed, it will already be obsolete, which means pending indefinitely.
(In reply to comment #1) > #2. The version of QtWebKit you are testing with, i.e. the one that came with > Qt 4.7.x, is very very old. Need to perform the test with QtWebKit >= 2.2 which > should come with Qt 4.8. libQtWebKit4-4.7.4+2.2.0 here. This should be ≥ 2.2, right?
(In reply to comment #3) > (In reply to comment #1) > > > #2. The version of QtWebKit you are testing with, i.e. the one that came with > > Qt 4.7.x, is very very old. Need to perform the test with QtWebKit >= 2.2 which > > should come with Qt 4.8. > > libQtWebKit4-4.7.4+2.2.0 here. This should be ≥ 2.2, right? Dunno what that versioning means. It could be that they are already compiling QtWebKit separately and are providing QtWebKit 2.2. You can verify that by checking the useragent string in the useragent configuration dialog. If you see AppleWebKit/533.x, then it is 2.2 or higher.
(In reply to comment #2) > (In reply to comment #1) > > Few things... > > > > #1. With QtWebkit 2.2, I do not see any difference when viewing the attached > > test case in Konqueror+webkit, Firefox or Chromium. Did you attach the correct > > test case ? > > Yes, and Firefox also does it wrong. > > <URL: http://input.mozilla.com/pl/opinion/2654409 > Then you should report it upstream as suggested in my previous response, because I get the same exact thing as in Firefox and Chromium as well.
(In reply to comment #4) > (In reply to comment #3) > > (In reply to comment #1) > > > > > #2. The version of QtWebKit you are testing with, i.e. the one that came with > > > Qt 4.7.x, is very very old. Need to perform the test with QtWebKit >= 2.2 which > > > should come with Qt 4.8. > > > > libQtWebKit4-4.7.4+2.2.0 here. This should be ≥ 2.2, right? > > Dunno what that versioning means. It could be that they are already compiling > QtWebKit separately and are providing QtWebKit 2.2. You can verify that by > checking the useragent string in the useragent configuration dialog. If you see > AppleWebKit/533.x, then it is 2.2 or higher. AppleWebKit/533.3
Bug WebKit 13159.
Link: https://www.webkit.org/b/13159