Skip to main content
Home Forums Silverlight Programming Programming with JavaScript IE/Firefox issues
3 replies. Latest Post by WynApse on October 24, 2007.
(0)
WynApse
Star
8436 points
342 Posts
05-10-2007 1:13 AM |
After the guys on AZGroups pointed out some issues with my GlyphMap conversion, I made some changes to it tonight in an effort to try to get it to work with Firefox. I detailed out the changes in the article itself: http://www.wynapse.com/Silverlight/Silverlight_GlyphMap_Utility.aspx
The deal is that it still isn't working 100% of the time. If I clear everything, then browse to the page, the Glyphs are not displayed, but everything else seems to work fine.. the canvas is alive, javascript is running.
If I wait a bit and do a reload, it appears to work... what is that all about?
This is straight JS, and the JS and xaml are on the page as well... can someone see what is going on?
Thanks!
-Dave
05-10-2007 12:03 PM |
I played with the Loaded= as opposed to "OnLoad" on the control last night, and if I removed the Loaded= from the main canvas, IE appeared to work about the same as Firefox usually does... so I'm convinced that my Loaded= code is not running in Firefox.. but I don't know why.
I'm hoping someone with good JS experience can see something I'm doing in the xaml_Page_Loaded function that is giving Firefox a fit.
The interesting thing is that if you browse somewhere then hit the back button, this loads up and runs just fine in Firefox... and I have had a couple times that it loaded up fine the first try, so it's confusing the &%**@ out of me.
Anybody?
geekpunk
Member
194 points
40 Posts
10-23-2007 6:51 PM |
did you find any resultion to this. I'm seeing the same behavior. The Loaded seems to fire fine in ie but never hits in firefox?
10-24-2007 4:32 PM |
I still see the Loaded not run on IE if I try enough times...
For example this page:
http://www.wynapse.com/Silverlight/Silverlight_GlyphMap_Utility.aspx
depends upon the Loaded= running to set up some things, and it doesn't always happen... not sure why!