I kept thinking about this, and I think I have some unimplementable poetry for a correct behaviour, and some implementable prose that would do as a substitute. The poetry is: whatever the user is attending to: after the re-render, it should be in the same place on the screen. It's unimplementable because: - we don't know where in the rectangle the user is attending - different parts of the rectangle can move in different directions -- eg folding up navigation links into a side-bar - parts of the rectangle can be forced to move horizontally, in ways that we would not be able to cancel out with scrolling The prose is: however far the (top of the) page is displaced from the anchor position, after the re-render, the top of page should be displaced by the same amount from the new anchor position. Do people think that this prose is a reasonable version of correctness? Regards, James. On 28/02/2015, James C <james.from.wellington at gmail.com> wrote:
Peripheral to the original issue, preserving smooth behavour of a form across a re-render would be an interesting (possibly in a slightly hair-pull way) problem.
The content of fields, cursor position, and keystrokes received during the re-render, would all have to be preserved.
I'm not volunteering.
Regards, James.
On 27/02/2015, John Found <johnfound at asm32.info> wrote:
On Thu, 26 Feb 2015 22:34:45 +0100 Andreas Kemnade <andreas at kemnade.info> wrote:
So a blank screen is your preferred way to fill out forms or should I rather wait some minutes before starting to work on the page? I do not understand your logic.
Waiting for the CSS prior to rendering the page, does not forbid switching CSS off, as you described. Both features can co-exists without any conflict.
My logic is that if the CSS files loads so slow as you describe (I still think it is a very, very rare case that can not rule the whole design), it is not important whether the rendering will happen twice or once - the page still will be not usable at all and you will need to disable CSS in order to get some usability at all. Notice, that nothing changes for your mentioned site, but on the normal, fast web sites, the screen flicker will be removed at all.
-- http://fresh.flatassembler.net http://asm32.info John Found <johnfound at asm32.info>
_______________________________________________ Dillo-dev mailing list Dillo-dev at dillo.org http://lists.dillo.org/cgi-bin/mailman/listinfo/dillo-dev