Custom Pagers will not work in a "teaser" block view

I do have a page with a view on it. There are a number of perfectly valid reasons to use this functionality.

In my case, it is a difference between how much of a node is being displayed on the front page vs. on its own dedicated page. When a webcomic is displayed on the front page, it does not display the full node, which consists of a comic transcription tool and on occasion some supplemental text -- but I still want the reader to be able to click on the next/previous links.

In other cases, it may be that someone wants to display a list of different categories of content while giving the reader the ability to page through those categories.

The custom pagers module links to full page nodes. I don't see why making those links available on a more limited view would somehow screw that up.

I'm going to go into a little bit more detail here to help illustrate why I feel this is a big. Keep in mind that one of the uses specifically mentioned for this module is "webcomic," and the de facto standard for webcomic paging is different from the way Drupal handles information.

Webcomic paging, to translate into Drupal terms, is strictly confined to a single taxonomy -- in other words, it is confined to the webcomic itself. It pages from "left" to "right", with "left" consisting of moving backwards in time (i.e., viewing earlier comics) and "right" moving forwards in time (i.e., viewing later comics).

I have a site that publishes three different webcomics, all of which have their own pagers. It is possible to have all three webcomics published to the front page on a single day, and if I choose to display them as full nodes then you will see all three webcomics, with their individual custom pagers, sitting on the front page.

Clicking the "previous" button for the Help Desk comic will take you to the full page node for the previous days Help Desk comic.

Clicking the "previous" button for the Kernel Panic comic will take you to the full page node for the previous days Kernel panic comic.

Clicking the "previous" button for the Old Skool Webcomic comic will take you to the full page node for the previous days OSW comic.

My readers don't find this confusing. That is exactly the functionality they expect from webcomic navigation buttons -- it conforms to the standard.

However, when my webcomics are published to the front page as full nodes they look like this:

http://ubersoft.net/comic/hd/2007/08/unwelcome-news

... without the comment section. In other words, they see:

- the top pager
- the comic
- the copyright info
- the bottom pager
- the comic transcript (if it has been entered)
- registered users will see the tool that allows them to enter a comic transcript

... and this takes up a lot of space. That is far too much to put in a block on the front page. All I want them to see is:

- the top pager
- the comic
- the copyright info
- the bottom pager

That will cut the size of the block in half.

The teaser view appears to have been designed to do just that, especially when you combine it with Content Templates. So why would it be so difficult to add custom pager functionality to this view? If the reason is purely aesthetic then I suggest that it should be the site designer who makes that decision. If there is a technical reason, I can't speak to that -- I just want to make clear that there are legitimate reasons for considering this a bug.