Custom Node interprets MaterialAttributes inputs as float3

It seems that the Material Editor's Custom nodes don't handle inputs of type FMaterialAttributes correctly, and instead interpret them as float3.

Using Material Attributes as an input to a Custom Expression causes the HLSL Translator to create multiple CustomExpression# functions, for each used member of the Material Attributes, rather than using FMaterialAttributes.

1. Create a material like this, where a MaterialAttributes struct is used as the input to a Custom node:
   [Image Removed]
2. Observe shader compilation errors and/or generated HLSL code indicating that the MaterialAttributes input is interpreted as being of type float3

How do I set a material as a post-processing material?

How does TextureRenderTarget2D get TArray<uint8> type data?

Why does the REMOVE method of map container remove elements have memory leaks?

How to delete some elements correctly when deleting an array loop?

What controls of umg have mouse wheel events in UE4.27?

What is the difference between Camera and CineCamera?

How to implement springarm components to scale according to mouse position in spawn?

How to use the.usf file in the ue4 engine Shader in the material?

What ConsoleCommand can be executed to improve the quality of pixel stream images?

Why does the volume fog disappear from a distant view?