JDK-8087886 : J2D pipeline does not implement proper handling of the subimage "isolate mask" control
  • Type: Bug
  • Component: javafx
  • Sub-Component: graphics
  • Affected Version: fx2.1
  • Priority: P5
  • Status: Open
  • Resolution: Unresolved
  • Submitted: 2012-01-28
  • Updated: 2018-09-05
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
tbdUnresolved
Related Reports
Relates :  
Relates :  
Relates :  
Description
The fix for bug RT-19208 introduced a new control on the drawTexture calls that draw a subimage that allows the caller to specify which edges to perform edge control overrides on.  Unfortunately all of the J2D calls ignore this parameter.
Comments
The main bug it gets by ignoring this parameter is that it isolates the subimage on all sides regardless of whether the caller wanted that behavior. Note that such behavior is extremely expensive to emulate with hardware textures so all support for the isolation was removed with the fix for RT-24566. Previously the J2D pipeline behavior may have been correct when the isolation was requested, but the public FX APIs had no way to request that isolation so it was only correct for a couple of internal 9-slicing cases that will need to be rewritten to use a different technique than internal sub-image isolation and the J2D pipeline will need to be updated to not do the isolation in any sub-image case.
02-11-2012

Out of time for 2.2, so target to Lombard.
10-07-2012

The isolation control was added while fixing RT-19208.
31-01-2012