QML WebEngineView canGoBack/Forward does not change for routing based on URL hash

Using the QML WebEngineView component, canGoBack and canGoForward changes are not notified when the URL hash fragment changes. Consequences are that we can't synchronize navigation UI (go back/forward) based on these properties. This behavior can be observed with the nano browser example:

1. launch the nano browser example directly on a website using fragment routing: /quicknanobrowser "http://dev.sencha.com/ext/5.0.1/examples/executive-dashboard/index.html"
2. click the left menu to navigate on the website (URL hash will change)

Expected result: "back" button should be enabled
Actual result: "back" button stays disabled

Same for the "forward" button:

1. launch nano browser example
2. enter URL of the previous website
3. click the left menu to navigate on the website (URL hash will change)
4. click the "back" button (website is routed to the previous hash)

Expected result: "forward" button should be enabled
Actual result: "forward" button stays disabled

Debug

When reading the QML implementation of the WebEngineView, the canGoBack and canGoForward properties are based on the loadingChanged signal. The webview doesn't load when the URL hash changes, which seems the reason why canGoBack/Forward never changes. A potential fix would be to use instead the urlChanged as NOTIFY signal?

    Q_PROPERTY(bool canGoBack READ canGoBack NOTIFY urlChanged)
    Q_PROPERTY(bool canGoForward READ canGoForward NOTIFY urlChanged)