Skip to main content

Bug Tracker

Side navigation

#7684 closed bug (invalid)

Opened December 02, 2010 05:00PM UTC

Closed December 03, 2010 08:48PM UTC

Timing problem

Reported by: jordi@ponttrencat.es Owned by: jordi@ponttrencat.es
Priority: undecided Milestone: 1.6
Component: unfiled Version: 1.4.4
Keywords: Cc:
Blocked by: Blocking:
Description

Changed site to use liquid-canvas (making buttons etc). With Firefox /Chrome all ok. IE (v8) does not render canvas correctly. About 70% does not show up, mostly ok when refreshing frame! (not 100%). Seems to depend on timing. Tracked down with simple canvas, directly using jquery, same problem. Saw you changed "ready: function" heavily from 1.3.2 to 1.4.4 but same error with both versions. Anything in preparation? I commented out: document.attachEvent("onreadystatechange", DOMContentLoaded);

to force "onload", seems to be better but NOT perfect.

Thanks for great job!

Attachments (0)
Change History (3)

Changed December 02, 2010 05:48PM UTC by jitter comment:1

owner: → jordi@ponttrencat.es
status: newpending

To be honest I couldn't quite figure out what your report is saying.

If the issue is with liquid-canvas then you should report the problem to the author of that plugin as this bug tracker is only for jQuery core issues.

If you think you found a problem in jQuery core then please provide a reduced test case (without any dependencies to plugins), which reproduces the issue you are experiencing, on http://jsfiddle.net. So that we can investigate this issue further.

Changed December 03, 2010 07:27PM UTC by jordi@ponttrencat.es comment:2

status: pendingnew

Could not definitely locate problem, could also be bad influence of plugin(s). Suggest to close ticket. Will try to investigate more.

Thanks Jordi

Changed December 03, 2010 08:48PM UTC by jitter comment:3

resolution: → invalid
status: newclosed

Closing per request of reporter. If you can provide more info and a reproducible test case which shows a bug in jQuery core we will be happy to further investigate the issue and eventually reopen the ticket.