JDK-8091956 : The code that validates sizes for textures internally is not consistent
  • Type: Enhancement
  • Component: javafx
  • Sub-Component: graphics
  • Affected Version: 8
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • Submitted: 2012-10-26
  • 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 :  
JDK-8102048 - Need to resolve the semantic of padding and how it can be implemented
Description
While fixing RT-24566, the texture padding semantics bug, we noticed that the code that handles all of the cases of dealing with non-power-of-2 textures, zero/edge/repeat padding, and maximum and minimum texture sizes was inconsistent across the pipelines and inconsistent even within the code of one of those pipelines.  We need to establish some consistent guidelines about how to deal with requests that are negative, 0, too large, or which go outside of those ranges after we adjust the dimensions due to platform restrictions.