| 1 | | Because this use case where thousands of shapes are created and destroyed during the app lifecycle is quite specific and due to IE bad memory management, a possible patch would be to recycle the ids of the destroyed shapes. This way, it would limit the number of intern strings the browser has to handle. \\ |
| 2 | | But since recycling ids makes an id not "unique" anymore, and therefore may have some possible impacts on existing application, |
| | 1 | A possible patch would be to recycle the ids of the destroyed shapes. This way, it would limit the number of intern strings the browser has to handle. \\ |
| | 2 | But since recycling ids makes an id not "unique" anymore, and therefore may have some possible impacts on existing application, and because this use case where thousands of shapes are created and destroyed during the app lifecycle is quite specific and due to IE bad memory management, the patch would need to be enabled via a dojoConfig flag. |
