mwyrzykowski

Results 197 comments of mwyrzykowski

Interaction regions can be outside of parent’s when overflow: hidden is set on the parent

Adding a test case and investigating the test failures this change causes

Interaction regions can be outside of parent’s when overflow: hidden is set on the parent

I limited the change to interaction regions, since the original patch broke a number of `overflow: scroll` event-region tests.

Interaction regions can be outside of parent’s when overflow: hidden is set on the parent

Clipping to fragment.backgroundRect instead of fragment.foregroundRect seems to have resolved the majority of the regressions

What OSes and hardware are we targeting?

> @mwyrzykowski has it always been the case that the M1 (Apple7) and M2 (Apple8) advertised support for mac1/mac2 feature sets/families (and therefore their capabilities) on macOS? Yes that is...

Should alphaToCoverageEnabled require a blendable format?

This could be worked around in metal possibly but before we do so, I want to clarify the expectation as the CTS does not appear to cover this case

Should alphaToCoverageEnabled require a blendable format?

That's right, the specific error from Metal is: ``` validateWithDevice:4343: failed assertion `Render Pipeline Descriptor Validation MTLRenderPipelineDescriptor with alphaToCoverageEnabled requires a float/unorm pixel format, but colorAttachments[0].pixelFormat(MTLPixelFormatRGBA8Sint) is not blendable ```

Should alphaToCoverageEnabled require a blendable format?

Yes that seems like a reasonable restriction

HW Clip Planes support

`[clip_distance]` supports 8 values, e.g., `float clipDistance [[clip_distance]] [8];`

Validation for setViewport should be `minDepth <= maxDepth`

cc @Kangz for insight

Texture types with f16, e.g. `texture_2d<f16>`

Metal allows this