Michael Schnell wrote:
On 11/29/2013 11:55 AM, Mark Morgan Lloyd wrote:
That goes back to some of the earliest Netscape versions, IIRC it was
originally used to update images periodically. While attractive, this
sort of thing can turn into a nightmare if the browser on an end
user's system leaks memory until an entire page (i.e. not just part of
the DOM describing the page) is forcibly reloaded- BTDT.
Do we still need to take into account that a browser is that limited ?
Browser technology has advanced a lot during the passed few years.
"Do we have to take into account that a browser might have bugs?"
Probably.
"Do we have to take into account that somebody might run a browser older
than we like supporting?"
Partly: at the absolute minimum to give him a sensible error message,
and ideally to provide some sort of usable UI even if it lacks the
"bells and whistles".
--
Mark Morgan Lloyd
markMLl .AT. telemetry.co .DOT. uk
[Opinions above are the author's, not those of his employers or colleagues]
--
_______________________________________________
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
