[mythtv] Ticket #8141: [PATCH] mythbrowser: Page up/down fix

Alec Leamas leamas.alec at gmail.com
Sun Mar 7 20:03:54 UTC 2010


On 03/07/2010 08:47 PM, Stuart Morgan wrote:
> On Sunday 07 Mar 2010 19:21:16 Alec Leamas wrote:
>    
>> On 03/07/2010 07:02 PM, MythTV wrote:
>>      
>>> Comment:
>>>
>>>    I think page up/dowm should move a page at a time. If you want finer
>>>    control then use the up or down arrows which move a 1/10 of a page.
>>>        
>> True. But users really expect to be able to read e. g. a long text by
>> simply using page up/down. And this just dont work as of today, there is
>> often a line which can't be read unless you use the arrows.
>>
>> At least Firefox and Chrome implements Page up/down by scrolling less
>> than a complete page. The same is true for OO writer.  Why should not
>> mythbrowser do the same?
>>
>> User requirements, the idea to do the expected and the actual
>> documentation all points to scrolling less than a complete page IMHO.
>>      
> Opera scrolls a complete page with PgUp/Down. You are right about Firefox, but
> it's about 90%.
>
> I guess you have to ask; should it be consistent with some (but not all)
> browsers, or consistent with the rest of mythfrontend where PgUp/PgDown moves
> a full 'page' in lists. I'm not voicing an opinion on how it should work, but
> laying out some of the facts and possible considerations.
>    
First of all, time to be a little polite. Really. I  *do* appreciate 
those of you taking time to evaluate and discuss my newbie patches. Thanks!

So, there are more browsers out there! Anyway, the difference is with 
the rest of myth is that when you scroll a page in a table, you never 
display a partial line at bottom. Eiter you see the line, or not. And if 
you can't see a line on current page, it will be on the next as I 
understand the situation.

But the browser is different. It just scrolls a number of pixels, and as 
a result both the first and last line might be hard to read. And making 
a complete page scroll, the line that was hard to read at the bottom of 
a page typically becomes equally hard to read at the top of next page.

The question is really if it should be possible to read a long page by 
only using page up/down. My own opinion, while not that interesing, 
should be obvious :-) OTOH, this is not really a Big Issue.

An even smaller issue is of course if a page scroll should be 75%, 90% 
or maybe 95%. I have really no educated  guess about this. I kept it 
rather low just to make a little closer to the documented 50%.

Cheers

--alec


More information about the mythtv-dev mailing list