naa koy ask bro,
naa koy desktop sample project then if akong i view sa firefox ok man sya.working and maka transact. pero if sa IE nko i open kay naay error... I dont know if unsa akong nabuhat sa code...
mao ni ang mga screen shots:
For Firefox:
For IE:
Notice that in FF kay ok ra while in IE, mu load sya but the taskbar is gone with errors... I wonder what did I do... hehehe
thanks daan bro...
try ug gamit javascript debugger for IE bro para ma-trace nimu asa dapit ang cause sa error...
ng gamit nko bro pero dili nko makita ang cause... libog kaau gamiton ang fiebuglite for IE
ni-refer na ka sa compatibility issues with IE ani sa ext-js forum? daghan bya compatibility issues sa IE 7.. i-try sa IE 8, kung if you encounter same problems ba..
ako, di ko murecommend gamit ug ext-js sa IE 7 or below kay daghan labad sa ulo.. even though mi-post ang ext-js na support sila sa IE 6, I require IE 8 as minimum kay mawala tanan problema..
most of the problems na encounter nko sa IE 7 kay javascript issues, like declaration of arrays or json objects using brace notation, naa difference gamay ang IE 7 compared to Firefox.. this difference will crash your IE 7 rendering, but firefox seems to accept it just fine.
ako ng gi refer sa forum sa una but katong last time kay na solve but with different project. karon gi try nko tong solution on my other project but no work at all. I am just referring it to others lng nga local programmers para madali ko ug sabot... anyways, labad jud sa ulo ang IE 7 lower especially sa browser compatibility in css and html.
Thanks kaau bro, Atleast it is working on firefox, buhatan na lang ug script na if dili firefox kay mg msg nga must only used firefox for better performance(which must not be) pero wala ta mabuhat...mabuang ta ug sinolve. hehehe...
unsa imong account sa forum sa extjs? ako diay si Muffinboy...
We used it in one of our projects, ASP.NET + Script# + ExtJs combo and it really sucked on browser compatibility especially IE. We have hard time debugging those issues with IE esp with IE6. Moreover, I will never recommend Script#, it will just give you nightmares. I would prefer a direct ExtJs slapped to an ASP.NET app or a server control that spits out an Ext js code. *end rant*
Anyway, bluedes already said it, check for Ext changelogs, there maybe some notes there that fixes your problem, a later version may fix it too.
Similar Threads |
|