I think this is working as intended. 
Use chrome.webNavigation.onReferenceFragmentUpdated:
https://developer.chrome.com/extensions/webNavigation#event-onReferenceFragmentUpdated

If I totally remove anchor e.g. abc.com/#Test -> abc.com
It is a totally new navigation, but still no onCommitted.

It does fetch the page from server.
You can check it in DevTools Network.

The page javascript fetches something from server, not the browser. 
Changing/adding the hash fragment never makes the browser itself fetch the page from server.
However, removing it completely should trigger onCommitted so it seems like a bug, indeed.

Please update the reproduction step for the correct one.

This primitive bug tracker doesn't support editing so you'll have to post the new repro steps yourself in a new comment.

Reproduction step:

1. Open any website: anything.com/#Test
2. Go to same website without anchor: anything.com

onCommitted is not fired while this is a new navigation.

Tested the issue on windows 7 using chrome version 58.0.3029.81 with the below steps

1.Opened Yahoo.com/
2.Go to anchor: yahoo.com/#Test
3.Changed anchor: Yahoo.com/#Other
4.Reload page with same anchor: anything.com/#Other
5. Observed that yahoo.com/#Test is loaded after reloading

Could you please  find the attached screen cast and confirm if anything missed here.
Please provide us the expected behaviour to triage the issue from test team end.

Thanks,

Deleted: 714434.mp4 1.8 MB

	714434.mp4 1.8 MB View Download

nn1436401@ could you please respond to the comment #11

The scenario is following:

1. Open background page of any extension.
2. Go to console tab
3. chrome.webNavigation.onCommitted.addListener(console.log, { url: [{ schemes: ["http", "https"] }] };)
4. Open www.yahoo.com/#ABC
5. Check you have committed event for the main frame. (frameId is 0)
6. Remove '#ABC' and enter -> www.yahoo.com/

In the background console you see many events but no event for main frame.

Thank you for providing more feedback. Adding requester "kavvaru@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Tested this issue using latest stable #58.0.3029.81 on Win 10 an unable to reproduce the issue as per the steps mentioned in comment #11

@Reporter: Could you please find the attached screen cast and let me know if I missed any steps from my end. If possible please attach a expected screen cast or screen shot for further triaging of the issue.

Thanks,

Deleted: May 25 2017 10-54 PM.webm 12.4 MB

	May 25 2017 10-54 PM.webm 12.4 MB View Download

Correction
==========

This issue tested on latest stable M58: 58.0.3029.110.

Thanks,

You had an error in the handler code in the console.

chrome.webNavigation.onCommitted.addListener(console.log, { url: [{ schemes: ["http", "https"] }] })


Attaching video:

Deleted: webRequestError.gif 904 KB

	webRequestError.gif 904 KB View Download

Thank you for providing more feedback. Adding requester "sandeepkumars@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Tested the issue on windows 7 using chrome version 58.0.3029.110.
Still getting the error in console.
Please find the attached screen shot and confirm if anything missed here.

Thanks,

Deleted: 714434.png 53.6 KB

	714434.png 53.6 KB View Download

As there is no action on this issue for long time closing this issue. Request you to update your Chrome to latest #66.0.3359.181 and verify. Feel free to file a new issue if the issue is still reproduced at your end.

Thanks!