Texture Property Node Returns Unexpected Values For Texture Object With Render Target Input

The texture property node returns incorrect values for texture objects that have a render target as its input. The correct value will be returned if a normal texture is used for the input instead.

1. Open a blank project
2. Crate a new material and render target in content browser
3. Open the material and add a texture object referencing the render target
4. Drag off from texture object and plug into Texture property node set to "Texture Size"
5. Test the output using a debug float 2 values node

RESULT

If you have texture size selected for the texture property node it will return 0 and for texel size 11111.1111 for both x and y.

EXPECTED
It returns the size of the render target in the case of a default render target it should be (256,256)

TextureProperty material nodes return (0,0) with render target input