Current core-overlay is attempting to focus itself as next! (bug)

[rodrigob]

What steps will reproduce the problem?

1. Create polymer element using paper-action-dialog
2. Call the_dialog.toggle() (dialog appears)
3. Call the_dialog.toggle() again (dialog dis-appears)

What is the expected output? What do you see instead?

I would expect no exceptions. Instead I get

"Current core-overlay is attempting to focus itself as next! (bug)"

and

Uncaught TypeError: Cannot read property 'removeChild' of null index.html:2102
Polymer.removeElement index.html:2102
Polymer.transitionend index.html:2529
(anonymous function) index.html:2788
b.fire polymer.min.js:13
Polymer.complete index.html:1986
(anonymous function) index.html:3037
listener index.html:2001

What version of the product are you using?

polymer: "0.15.5"
paper_elements: "0.6.1"
Dart SDK version 1.8.5

On what operating system?
Ubuntu 14.04.1 LTS

What browser (if applicable)?
Dartium, but seems to appear on other browsers too.

Please provide any additional information below.
After the exception, the dialog still works, but its size is wrong.

Bug also reported at https://code.google.com/p/dart/issues/detail?id=22281

[rodrigob]

Any clue of what could the cause of this issue ? How should I approach it ? Any suggested work around (other than not using polymer) ?

[jakemac53]

I think that the only workaround right now to to insert a delay in between the calls. Afaik this issue happens when calling toggle() during an active transition.

[rodrigob]

What do you mean by "active transition" ? Even when waiting long time between step 2 and 3 the issue appears.

[rodrigob]

My current work around is using paper-dialog instead of paper-action-dialog, and <div horizontal justified layout> to place the buttons somewhat properly.

[jakemac53]

Weird, in the past I have only seen this when calling toggle() in quick succession. This might be a separate bug.

[Andersmholmgren]

FYI I've seen this in my logs over quite a long period but largely ignored it as the app seemed to work fine. I'm looking more closely at it now since my app is having issues