Closed GoogleCodeExporter closed 9 years ago
This is reproducible using the Live example.
Original comment by justin.e...@gmail.com
on 27 May 2011 at 1:18
Original comment by justin.e...@gmail.com
on 27 May 2011 at 1:19
An important issue with IE was that the animation of the value was fired every
40 msec without waiting for the frames to redraw. This can set the cpu usage to
100% even on a fast machine. This was solved in r23.
Original comment by dragos.tihauan
on 29 May 2011 at 9:36
Unfortunately the flickering still occurs when viewed online from our server.
However, the live example works smoothly and without any flicker on the same
laptop!
So I guess our Internet server is to blame - on a ping test, the average speed
is 130ms but I don’t know if that is the root cause?
Original comment by ypipe...@googlemail.com
on 1 Jun 2011 at 8:16
Original comment by dragos.tihauan
on 4 Jun 2011 at 9:48
Is it possible that you could have been using a cached version of gauge.js
during your follow-on testing? Could you please confirm this is still a problem
after clearing your browser cache?
Also this may be asking a lot, but if this is still an issue for you, would it
be possible to post a link to this server or another one that can demonstrate
the problem?
Original comment by justin.e...@gmail.com
on 8 Jun 2011 at 1:45
I think the flickering is caused because there is no doctype in the website I
am using (I'm not sure why this is missing, the website is old and uses
frames). If you delete doctype info the flickering occurs on the live example,
but if you add <!DOCTYPE HTML>, the flickering goes away.
So I concluded the flickering is due to the Doctype not being declared.
Unfortunately I cannot add or edit the Doctype, as my software editor only
allows access to the HTML code between the <body> tags.
Therefore the flickering problem is due to lack of doctype declaration in our
software and not a defect in the JSGauge.
Thanks again for looking into this issue.
Original comment by ypipe...@googlemail.com
on 8 Jun 2011 at 7:17
You're welcome - Thank you very much for clarifying!
Unfortunately doctype is an important part of the page - I have seen similar
issues with other JavaScript libraries when a doctype was not specified. This
is outside the scope of this ticket, but perhaps as a workaround - if you
cannot change the doctype directly - perhaps you could insert an iframe
containing the gauge? Anyway, I hope you find a way around this particular
issue...
Original comment by justin.e...@gmail.com
on 8 Jun 2011 at 8:17
Original comment by dragos.tihauan
on 16 Jun 2011 at 7:45
Original issue reported on code.google.com by
ypipe...@googlemail.com
on 27 May 2011 at 7:57