yep, this started happening a few weeks ago.

please help us get rid of this 

So..

Swipe in a downwards angle, and the notification just goes away.

Swipe in an upwards angle, and the application opens.

As far as I can tell, this is not documented anywhere.

It doesn't let you swipe down or up only side to side keep in mind this is a chromebook R11 Acer

I'm not saying swipe up or down (that scrolls the notification list, no?)

I'm saying swipe at an angle, the direction of your swipe, even if a single pixel, affects the swipe action.

Swipe from the top left corner, to the bottom right corner, and the notification will dismiss as intended.

Try it, I swear it works.

I'm not 100% sure, but I believe the code that is relevant to this is here:

https://github.com/chromium/chromium/blob/c222ea2375344f02df309efb8d84f481b219fe51/ui/message_center/views/slide_out_controller.cc

Look for kScrollRatioForClosingNotification.

It looks to me like it's checking for a scroll amount, in addition to the slide gesture, and then toggling some logic depending on the direction if the scroll met the threshold.

Here's someone else who found the same behavior, too, you don't just have to take my word for it:

https://productforums.google.com/d/msg/chromebook-central/nZW7SlPgk_U/Bj55eTE9BAAJ

Bug confirmed on:
● Platform: Google Pixelbook (eve) in
● Configuration: Tablet Mode, with both fingertip and Pixelbook Pen swipe-to-dismiss gestures
● Google Chrome: 65.0.3325.209 (Official Build) (64-bit)
● Platform: 10323.67.5 (Official Build) stable-channel eve

As far as my understanding goes, swiping right on a notification ought to just dismiss it - and this works correctly on notifications from Chrome, such as a new video notification from www.youtube.com (in a channel to which I'm subscribed in YouTube). At whatever angle I swipe right, the Chrome notification just gets correctly dismissed - without opening or foregrounding the Chrome browser.

But with notifications from Android apps, the novel bugged behaviour shows up as follows:
● swipe right at an upward angle (eg: swipe from bottom-left to top-right) - the notification is dismissed AND the Android app INCORRECTLY opens in the foreground (just as if the notification had been tapped on to open it, rather than swiped right to dismiss it), and this bugged behaviour therefore requires the incorrectly opened Android app to be manually closed... ie: WRONG!
● swipe right at an downward angle (eg: swipe from top-left to bottom-right) - the notification is CORRECTLY just dismissed, and the Android app does NOT open... ie: RIGHT!

As far as I can tell, this new developer-created bug was introduced at the Chrome OS 65 stable channel update, in that this bugged behaviour was not present in stable channel Chrome OS 62, 63, and 64.

Although swiping right at a downward angle on Android app notifications is an effective workaround for dodging this bug's ill effects, the Chrome OS development team REALLY need to please FIX this annoying bug, so that Chrome OS is once again restored to its previously reliable state.

Samsung Chromebook pro with official build. Started about 4 weeks(ish) ago, hard to remember because I thought I was swiping incorrectly. Just noticed that ALL android apps just start when I do a proper and deliberate swipe. Adding to this thread to trigger some weight to the issue. This needs fixing.

Crash after swiping as well now on Beta 67.

840119 - Crash after clicking X to dismiss a notification Beta 67 - chromium - Monorail
https://bugs.chromium.org/p/chromium/issues/detail?id=840119

Acer Chromebook R11 ,same issue of swiping ,apps opening

Have had this bug with ChromeOS stable since late/mid March and it's now May. I'm surprised there still hasn't been addressed. I almost always end up using the notification overflow / three line (remove all notifications) button all the time now to avoid opening apps I don't want to remove. 

Enabled Beta channel in April and none of them have added fixes to date. 

Can someone please address this bug?  It has been happening since early April and has been ignored except by those of us reporting and starring it. UI now crashes when Android notifications are swiped away.

Maybe the crash in #15 related to http://b/79705621 (internal)  https://crbug.com/842705#c2  ?

Re #15, #16: I believe the crash is Issue 833533 and is already fixed.

I've been seeing this as well (main issue, not the crash)

It seems to only occur for notifications from ARC++, but consistently on all of them.  Clearing with the "Clear all" icon at the bottom works as expected, but swiping away an individual android notification launches it.

Seen on M68 on eve and samus

FYI: Issue on ARC notification is already fixed:  Issue 844120 

Thanks! Verified this fix hasn't made it to my device yet so I'll be looking forward to it :)

I think it's probably safe to close as fixed or a dupe of  Issue 844120 . The OP mentions "apps" opening rather than web pages and the linked product forum post in #7 references arc++ apps specifically.

Assuming it's fixed given we don't receive similar feedback recently.

This is indeed happening still, with the latest Chrome OS update that changed to the new UI, so yes... it still happens.