KhronosGroup / KhronosGroup/Vulkan-Docs
Not clear if scaled min and max equal normal caps if scaling not supported
Open
System Integration
- Dominant language
- JavaScript
- Stars
- 3.3k
- Forks
- 549
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 2
Description
It is not immediately clear if `VkSurfacePresentScalingCapabilitiesEXT::minScaledImageExtent` equals `VkSurfaceCapabilitiesKHR::minImageExtent` if `supportedPresentScaling == 0`. Or whether the value can be garbage in that case.
Contributor guide
Research direction
Review the descriptions of VkSurfacePresentScalingCapabilitiesEXT and VkSurfaceCapabilitiesKHR, focusing on minScaledImageExtent, minImageExtent, and supportedPresentScaling. Clarify in the specification whether unsupported scaling makes the scaled extents equivalent to the normal caps or leaves them undefined, and ensure the resulting wording answers the issue directly.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100