Because chrome is mostly used for debugging during the development process, debugging is rarely performed in ie (both of them should be taken into account now), and the page in ie cannot be loaded normally at the time, I want to cry when I see the error reported by ie, and I don't even have the wrong stack information (this is really bad for ie). I have been using ExtJS for nearly a year, also encountered a lot of strange problems, the most impressive is the problem that ExtJS shows in ie. Because chrome is mostly used for debugging during the development process, debugging is rarely performed in ie (both of them should be taken into account now), and the page in ie cannot be loaded normally at the time, I want to cry when I see the error reported by ie, but I don't even have the stack information (this is really bad for ie. I tried N multiple methods and found that the cause of this problem (more than 90% of the possibility) is that an English comma ',' is added to the js array ',', this is no problem in chrome and Firefox, as shown in the following code:
The Code is as follows:
Var win = Ext. create ('ext. window. Window ',{
// Some code is omitted here
//........
Items :[
{
Title: 'hello ',
Width: 100,
Height: 100
},{
Title: 'World ',
Width: 100,
Height: 100
},{
Title: 'foo ',
Width: 100,
Height: 100
}, // Note the English comma here. No error will be reported in chrome and Firefox.
]
// Some code is omitted here
//........
})
This is a difference in browser processing for arrays. When writing code, you should pay attention to this issue. If you have any similar problems, you can try to find them and you may be able to solve them. This is the problem I have met three times. (End) ^_^
