Webkit Drag and Drop shifts event focus to iframe document

[Michael Camden]

I've only tested this in webkit, but it's a fairly annoying problem. After dragging text from one CKEDITOR instance to another, events are no longer fired properly on the parent window. I've attached a very simple example of this problem.

1. Click on the 'Click to test' button. It will fire an alert with the message 'Test Successful'.
2. Click the 'Click to replace' button. This will create two instances of CKEDITOR on the page.
3. Drag text from the first instance to the second instance.
4. Click on the 'Click to test' button. Nothing will happen.

In Chrome, if you repeat step 4, the message will now appear. In Safari, the button will never fire the message.

[Michael Camden]

Akismet wouldn't allow me to upload the HTML file, so here is a link. ​http://michaelcamden.me/safaridnd.html

[Jakub Ś]

In my opinion this is not a valid bug. This is just how webkit works with CKEditor.

First of all the behavior in Chrome is the same as in Safari. The second click worked in both browsers. The event could not be fired because focus was on editor, the first click after drag moved the focus to the button and the second click fired the event.

I'm confirming it in case if anyone else has different point of view on this.

[Michael Camden]

I disagree with your comment on the behavior. From my tests Chrome successfully shifts the focus back to the parent window on the first click, so the second click works. I am testing on Windows 7, Chrome version 12.0.742.91, Safari version 5.0.5.

If this isn't a valid bug, could you offer some suggestion on how to work around this issue?

[Jakub Ś]

Page from the example

[Jakub Ś]

Maybe got to quick with the comment. If I put focus on the editor by simply clicking on it and then click the button, event is fired. So maybe this ticket is valid after all.

But the results were consistent on both browsers in my case. Second click fired alert window on safari and chrome.

[Michael Camden]

I've just tested Safari, and it now behaves the same as Chrome. Any updates on the progress of this bug?

[Michael Camden]

Any progress on this?

[Michael Camden]

Any progress on this?