ID 373128 - Setting the ReadGeo frame range does not set Input frame range

Problem summary
Within the ReadGeo node , the Nuke Online Help documentation states that setting the Start frame and End frame of the Node will set the Input framerange when displayed.

https://learn.foundry.com/nuke/content/reference_guide/3d_nodes/readgeo.html?Highlight=readgeo

This behaviour does not appear to occur since Nuke9.0v9, where setting the Framerange would alter the Input range.

Customer reported version
11.2__11.2v4

Customer reported platform
windows10

Steps to reproduce

1) Open Nuke, create a ReadGeo node

2) Import an object into the ReadGeo node

3) Set the View to the ReadGeo node, and the view mode to Input

4) Set the Frame Start & End knobs within the ReadGeo to 0-10

Result: The View framerange will stay at the Global range.

Workaround
Create a FrameRange node underneath the ReadGeo node.

Reproduced by support

This bug has been reproduced in:
Nuke11.2v4 - Windows 7 - Mac10.13 - CentOS6.9
Nuke11.2v1 - Windows 7
Nuke11.1v4 - Windows 7
Nuke11.1v1 - Windows 7
Nuke11.0v4 - Windows 7
Nuke11.0v1 - Windows 7
Nuke10.5v7 - Windows 7 - Mac10.13 - CentOS6.9
Nuke10.5v1 - Windows 7
Nuke10.0v6 - Windows 7
Nuke10.0v1 - Windows 7 - Mac10.13 - CentOS6.9 - regression

Unable to reproduce bug in:
Nuke9.0v9 - Windows 7 - Mac10.13 - CentOS6.9

Earliest version tested
- This issue no longer appears in this version and has regressed

Expected behaviour
Setting the framerange on the ReadGeo node should set the Viewer Input framerange

Actual behaviour
Setting the ReadGeo framerange does nothing