Run this test on 6u10 on javafx1.0 runtime with Direct3D pipeline disabled
(if on windows), you'll see artifacts on the edges of the text rendered with
the effect:

import javafx.application.*;
import javafx.scene.paint.*;
import javafx.scene.*;
import javafx.scene.text.*;
import javafx.scene.effect.*;

Frame {
    title: "MyApplication"
    width: 600
    height: 200
    closeAction: function() {
        java.lang.System.exit( 0 );
    }
    visible: true

    scene: Scene {
        fill: Color.LIGHTBLUE
        content: [
            Text {
                effect: DropShadow{offsetX:3 offsetY:3 radius: 18 color:Color.WHITE}
                font: Font.font("Arial",FontWeight.BOLD,40.0)
                fill: Color.web("xF2F2F2")
                x: 20, y: 70
                content: "Text with the DropShadow"
                fill: Color.WHITE
            },
            Text {
                font: Font.font("Arial",FontWeight.BOLD,40.0)
                fill: Color.web("xF2F2F2")
                x: 20, y: 130
                content: "Text without the effect"
                fill: Color.WHITE
            }
        ]

    }
}

The issue is very similar to one described in 6728834, but this one is SW
pipeline only.
Posted Date : 2008-09-16 19:02:18.0

N/A

The original test case for 6728834 didn't show the problem with SW-rendered
text so I assumed that the sw lcd loops can handle destination with alpha.
But the problem becomes apparent in the test in the descripion.

The fix is the same - add a check for opaque destination to SurfaceData.canRenderLCDText().
Posted Date : 2008-09-16 19:02:18.0