Thanks for the report.  Could you help us understand your use case?  Do you find yourself having to deactivate all breakpoints frequently?

The behavior of "activate all breakpoints when a new one is set" has been around since at least 2012 [1], and I think many other users may be surprised if it changes.

[1] https://chromium.googlesource.com/chromium/src/+/ad2d400d72d8aea5acd459f121b5146e38fd2ad0%5E%21/#F2

Well.. it's an odd UI behavior that no one has reported! Why would clicking on a single breakpoint reactivates all the rest? There's no relationship between the breakpoints. If I want to reactive them, I can hit ctrl-F8 or right click on the breakpoint section and choose that option from the context menu.

My use case is that I don't want tens of breakpoints getting hit when I run the app when I am interested in one breakpoint and one section of the code. If you know of a better way to deactivate/reactivate a single breakpoint while the other breakpoints stay deactivated, let me know.

In Visual Studio, when I disable all the breakpoints, then I click on one, only that one gets activated. The rest of the breakpoints are not affected. That's the correct behavior and that's how I expect Chrome to behave. Maybe I am used to VS and I find Chrome's behavior odd but I just want the deactivated breakpoints stay deactivated without friction.

Actually there are two issues in Chrome. 
#1 Clicking on a deactivated breakpoint, deletes it. It should get activated instead. 
#2 Clicking again reactivates all the rest. I can deal with #1, but #2 is annoying.

Please check this issues in latest Chrome Canary, we fixed couple problems in breakpoint management. Feel free to open another issue if it is still a problem.
To reactivate disabled breakpoint you can click in gutter with Shift.