See the URL - the log for this file has no indication at all that the file got deleted or which changeset that happened in. It'd be nice if hgweb did the equivalent of hg log --removed.
Even if that would make it much slower?
I think "not misleading" is more important than "fast". How slow would it be?
Try hg log <file> vs. hg log --removed <file>. (The first is O(file changes), the second is O(number of csets in the repo)).
That seems like an amazingly inefficient implementation for a common operation... How about making this the default if the file doesn't exist on the tip anymore?
Yeah, it's a little bit silly. We might be able to do something like that, not sure if 'tip' is the best reference (f.e. in the face of named branches).