Hey Richard,
true I don't provide a global default for the display type. I thought about this, but then decided against it, because it's just one configuration too many that I didn't consider pulling it's own weight and being to complicated. The user's thinking would need to be very nested to understand that. This wouldn't be an issue for programmers, but for people who don't program I consider this too complicated. It would also be more inconsistent.
Regarding the change of behavior, you're right. Before it was "broken". When choosing "feed content + mobile web page" the default behavior for display type would need to be to show the mobile web page on display. I didn't check for that in my code and I didn't realize that, because on my phone I use "feed content" as default. Anyway, now that a user reported this issue I fixed it and it's more consistent now. But you are not the first to complain about the change ;-)
Now adding another global configuration option would make the display type options more inconsistent and complicated. Currently we have those options "feed", "web", "as download type". At least I would need to add "use global default". And would that be the default? That would mean that every feed that I set to a different download type than the default would need an adjustment of the display type, if it not also is the global default. This breaks locality for this setting.
I hope you understand.
Btw. the rendering of the mobile web page is really fast in my opinion. You feel differently? Also you can already read the header when the rendering starts, so that I, personally, use this to quickly scan through my articles.
Cheers,
Mariano