- From: gked <notifications@github.com>
- Date: Mon, 01 Aug 2016 18:04:29 -0700
- To: w3c/editing <editing@noreply.github.com>
Received on Tuesday, 2 August 2016 01:08:30 UTC
Edge has bugs in this area. Event sequence it fires is different from the rest: - drop - dragend - partial DOM update ( img element is being inserted after foo but not being removed before foo) - dragend - input -DOM update We'll fix the issue on our side as the behavior of the rest of the browsers makes sense. To Gary's second comment, Edge does update the DOM after dragend is being fired but for images. This is probably why Edge tries to update the DOM once dragend is fired. --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/editing/issues/134#issuecomment-236760262
Received on Tuesday, 2 August 2016 01:08:30 UTC