1. Load http://iop1.nokia-boston.com/CSS/index.html 2. Select CSS3_Text link. 3. Select the following link and observe its behavior: Link 1: 3.CSS3-Text: 'text-shadow' Property Link 2: 4.CSS3-Text: 'text-shadow' Property Link 3: 7.CSS3-Text: 'text-shadow' Property Link 4: 8.CSS3-Text: 'text-shadow' Property Link 5: 13.CSS3-Text: 'text-shadow' Property ACTUAL RESULTS: Link 1 and 2: Blue color shadow text is seen. Link 3: Black color shadow text is seen. Link 4: Multiple shadow text is seen. Link 5: Red shadow is not seen. Other info: Issue is observed on QtTestBrowser. Issue is not observed on Google Chrome browser. EXPECTED RESULTS: Link 1 and 2: Blue color shadow should be seen. Link 3: Grey color should be seen. Link 4: Multiple color shadow should be seen Link 5: Red shadow should be seen.
Created attachment 73249 [details] Failure test cases camparison between QtTestBrowser and Chrome Actually, we just have one issue: Looks like currently QtTestBrowser doesn't support "blur" in shadow. "[Blur-radius]: A length value indicating the boundary of the blurring for the current text-shadow effect." Need to investigate why?
Those test cases works fine on qt4.7+webkit trunk(linux). I investigated and found qtwebkit missed some patch like r65876 which for text blur, I know we have some patchs about shadow, r65876 is one of them.
Fix required for Qtwebkit 2.1/2.2
Everything works well with trunk. See the master bug https://bugs.webkit.org/show_bug.cgi?id=34479 for all the shadow handling in Qt. *** This bug has been marked as a duplicate of bug 34479 ***
(In reply to comment #3) > Fix required for Qtwebkit 2.1/2.2 This bug is blocking the 2.2 release but is marked as closed/duplicate of bug 34479. Bug 34479 on the other hand depends on 20 other smaller bugs. I'm removing the dependency, as it should be added on bug 34479 or to a small set of patches if we really decide to cherry-pick/backport this feature (or part of it).
(In reply to comment #5) > (In reply to comment #3) > > Fix required for Qtwebkit 2.1/2.2 > This bug is blocking the 2.2 release but is marked as closed/duplicate of bug 34479. > Bug 34479 on the other hand depends on 20 other smaller bugs. > I'm removing the dependency, as it should be added on bug 34479 or to a small set of patches if we really decide to cherry-pick/backport this feature (or part of it). It seems really hard to cherry-pick the patch of bug 34479 as it's dependent on too many other patches. Is it possible we add this feature to a later release that's off the trunk?