Opened 17 years ago
Closed 15 years ago
#550 closed Bug (fixed)
IE fails the _tests/manual/fckeditorapi
| Reported by: | Alfonso Martínez de Lizarrondo | Owned by: | |
|---|---|---|---|
| Priority: | Normal | Milestone: | CKEditor 3.0 |
| Component: | General | Version: | SVN (FCKeditor) - Retired |
| Keywords: | Confirmed IE | Cc: |
Description (last modified by )
IE doesn't fire the unload event of the inner frame until the whole parent window is unloaded. Simplified testcase available in [365].
This means that even if an instance of FCKeditor has been removed it's still available in the FCKeditorAPI.__Instances object.
Change History (5)
comment:1 Changed 17 years ago by
| Description: | modified (diff) |
|---|
comment:2 Changed 17 years ago by
| Milestone: | → FCKeditor 3.0 |
|---|
comment:3 Changed 17 years ago by
Yes, you're right. But it can take more than just a seconds, even some minute. I guess that they only do it on garbage cleaning and it can take a while.
comment:4 Changed 16 years ago by
| Keywords: | Confirmed IE added |
|---|
comment:5 Changed 15 years ago by
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
For V3, we have implemented the "destroy" function to take care of this issue.
Note: See
TracTickets for help on using
tickets.
Actually, it is not the IE doesn't call unload. It instead "delays" its call. It doesn't happen in the right moment that the window is removed, but a few seconds after it.
Just try it with _test/manual/fckeditorapi... you will see that if you create two instance, and remove one of them, the array will still have two instances. But, wait a little and click the update button again... wait again, and update again... you will check that, unexpectedly, the remove instance will be removed from the array.
I still have no idea how to handle this thing. Maybe a combination with "onbeforeunload", but we still have to investigate it deeper. Targeting to the 3.0 for now.