This has been reported to the website support team and we are looking into it. In the meantime, please add your votes from the list view or by commenting on that idea.
You can see Statuses by filtering the main list.
Critical Path using a Start-to-Finish predecessor
This is a scenario for projects where the finish date of the last task is dependent on the start date of a task/milestone (most likely from another project). For example, if the project is to decommission an application then disabling the application (last task) cannot occur until the new application goes live (start date of a task/milestone from another project). This requires an SF relationship in the predecessor column of the last task.
In this case, the issue is that when using a Start-to-Finish (SF) relationship in the predecessor column, the critical path for the entire project disappears. The only rows on the critical path are the two rows referenced in the SF relationship (again, in a scenario where those two tasks are the last ones in the project). It would be helpful if the critical path leading up to the SF relationship was maintained. This would also apply to certain project scenarios where the SF relationship was in the middle of the project. Pro Desk evaluated this and suggested that I submit it as an idea. Thank you.