I’m not sure about this, but since the fragment identifier is not sent to the server, I would’t be surprised if it wasn’t available in the webRequest handlers either.
The fragment identifier is only relevant when displaying the page, not when fetching it, so “blocking” pages based on it doesn’t really make sense. Also, it can very easily change while a page is being displayed.
One thing you could do is not display the page based on its current fragment identifier. There are several ways to achieve that, one is this: