[MD Bookmarks] Fix JS closure compile for paper-toast.

[MD Bookmarks] Fix JS closure compile for paper-toast.

This CL fixes a case with the closure script where concatenating
IronOverlayBehavior before an IIFE would cause the compile to fail
because IronOverlayBehavior ends with an @param declaration which is
expected to be true of the first thing in the next file.

This has been fixed by adding a jsdoc comment between concatenated files.

BUG=725786
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation

[calamity, 2017-05-25 06:40:06]

Description was changed from

==========
[MD Bookmarks] Fix JS closure compile for paper-toast.

This CL fixes a case with the closure script where concatenating
IronOverlayBehavior before an IIFE would cause the compile to fail
because IronOverlayBehavior ends with an @param declaration which is
expected to be true of the first thing in the next file.

This has been fixed by adding a jsdoc comment between concatenated files.

BUG=725786
==========

to

==========
[MD Bookmarks] Fix JS closure compile for paper-toast.

This CL fixes a case with the closure script where concatenating
IronOverlayBehavior before an IIFE would cause the compile to fail
because IronOverlayBehavior ends with an @param declaration which is
expected to be true of the first thing in the next file.

This has been fixed by adding a jsdoc comment between concatenated files.

BUG=725786
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:closure_compilation
==========

[calamity, 2017-05-25 07:38:21]

calamity@chromium.org changed reviewers:
+ dbeam@chromium.org

[calamity, 2017-05-25 07:38:22]

Hey,

You can patch in https://codereview.chromium.org/2898303004/ to see in what way
the compiler breaks.

PTAL, thanks!

[Dan Beam, 2017-05-30 23:32:58]

hmmmmmm

what's the expanded code look like?  isn't this a legit problem if we were to
ever try to minify the code?

[calamity, 2017-05-31 02:58:23]

On 2017/05/30 23:32:58, Dan Beam wrote:
> hmmmmmm
> 
> what's the expanded code look like?  isn't this a legit problem if we were to
> ever try to minify the code?

......

  /**
   * Fired after the overlay closes.
   * @event iron-overlay-closed
   * @param {Event} event The `event.detail` is the `closingReason` property
   * (contains `canceled`, whether the overlay was canceled).
   */

})();
</** */ added here>
(function() {
      'use strict';

      // Keeps track of the toast currently opened.
      var currentToast = null;

      Polymer({
        is: 'paper-toast',

.....

What kind of case are you thinking will be affected when minifying? I'm pretty
sure stray annotations will just be ignored and nothing too interesting should
change afaict.

[Dan Beam, 2017-06-06 02:18:32]

still need this?