Closed MarkStega closed 11 years ago
I would start by debugging the JavaScript in the chrome debugger and then in the ie/ff debugger and try to see where things are different. I don't have the project handy to try it and I'm not exactly clear from the screenshots as to where the issue is. It could also be as simple as a CSS issue.
Sent from my Windows Phone
From: MarkStegamailto:notifications@github.com Sent: 11/19/2013 11:43 AM To: nikhilk/scriptsharpmailto:scriptsharp@noreply.github.com Subject: [scriptsharp] Firefox/IE/Chrome rendering diffference (#408)
I am looking for a bit of advice. I built the KOWorld demo and it worked. I then set my sights on Todo and had odd behavior in Chrom. I am not looking for a solution, but instead, how one approaches this kind of issue in the Script#/jQuery world.
Chrome (2nd item has been checked as complete, text went from '456' to 'on'; no check persists; 'Clear completed' button does not appear)
Firefox: (1st item checked):
IE: Essentially the same as FF
Reply to this email directly or view it on GitHub: https://github.com/nikhilk/scriptsharp/issues/408
In general, the debugging story for script# generated scripts should be the same as debugging hand-authored script.
I'll close this out as it seems to be a general question, but if you do find a bug in the sample, please help fix it/re-open this with the result of investigation as a sample issue.
I am looking for a bit of advice. I built the KOWorld demo and it worked. I then set my sights on Todo and had odd behavior in Chrom. I am not looking for a solution, but instead, how one approaches this kind of issue in the Script#/jQuery world.
Chrome (2nd item has been checked as complete, text went from '456' to 'on'; no check persists; 'Clear completed' button does not appear)
Firefox: (1st item checked):
IE: Essentially the same as FF