JDK-8102048 : Need to resolve the semantic of padding and how it can be implemented
  • Type: Enhancement
  • Component: javafx
  • Sub-Component: graphics
  • Affected Version: 8
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2012-08-29
  • Updated: 2015-06-16
  • Resolved: 2012-10-26
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.
JDK 8
8Fixed
Related Reports
Blocks :  
JDK-8119646 - Beagleboard: Perspective Effect isn't render correctly
Blocks :  
JDK-8125338 - Beagleboard: DropShadow Effect isn't render correctly
Blocks :  
JDK-8116203 - EGLFB: MouseEventsSample - graphical artifacts
Relates :  
JDK-8088905 - New "shared textures" do not share pixel update flags as well as they should
Relates :  
JDK-8087886 - J2D pipeline does not implement proper handling of the subimage "isolate mask" control
Relates :  
JDK-8101854 - The Prism Graphics ISOLATE mechanism may no longer be needed
Relates :  
JDK-8125776 - ImageDataTest: IllegalArgumentException
Relates :  
JDK-8091956 - The code that validates sizes for textures internally is not consistent
Relates :  
JDK-8125525 - 8.0-graphics-scrum-h242: 48% (16.70 fps) performance regression in GUIMark2.Bitmap on MacOS
Description
We need to resolve when and how padding is applied on the es2 pipe. Our attend to remove padding have generated a series of issues (bugs) on the embedded devices. This is due to GL_CLAMP_TO_BORDER isn't available on OpenGL ES2 and NPOT isn't supported on some of the device.
Comments
The semantics have been resolved with the following changesets and most of the dependent bugs should not be fixed on embedded devices, but a notable exception is the DisplacementMap effect which does not appear to have been caused by padding issues. In the rt-closed repository: changeset: 17338:5f3e7add1a30 date: Fri Oct 26 15:47:24 2012 -0700 summary: Fix RT-24566: Resolve semantics of texture padding. In the rt repository: changeset: 1829:3626aad4f2a5 date: Fri Oct 26 15:49:05 2012 -0700 summary: Fix RT-24566: Resolve semantics of texture padding. There are no unit tests for this particular bug (resolving our internal semantics) because it is entirely an internal bookkeeping and module interfacing change and should be covered by standard QA testing. The various dependent bugs may have unit tests for their individual problems, though.
26-10-2012
Impacted Beagle demo
29-08-2012