This only happens in WebKit-based browsers (e.g. Safari, Chrome). But not in their nightly builds. Probably just a bug that has already been fixed.
Connection speed seems to be irrelevant. Markus On Feb 10, 1:11 pm, Markus <[email protected]> wrote: > Hi Richard, > > On Feb 10, 12:08 pm, riccardo <[email protected]> wrote: > > > On Wed, Feb 10, 2010 at 02:42:31AM -0800, Markus wrote: > > > I am looking for an explanation of an issue I reported some months > > > before but which stopped showing up. At the moment I have exactly the > > > same BoltWire files (3.3.6) on two servers and they seem to build/ > > > render pages differently. > > > I just opened them both and could not see any difference (from central > > London). > > Just tried Firefox and it did not flicker. > > > This is unlikely to be a boltwire issue. It probably varies depending on > > net conditions. Are the servers using identical hardware and OS? Are their > > loads identical? If not, they may dispatch the pages at different speeds, > > with pauses in different places. The variation could be introduced at any > > point ont he route. > > The servers are not identical. You are probably right that the > dispatching differs causing browsers to render the pages differently. > I wonder if there's some workaround (except making the wrapper color > white too). > > Markus -- You received this message because you are subscribed to the Google Groups "BoltWire" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/boltwire?hl=en.
