Since the problem in chrome does not seem to be fixed soon, and the will-change: opacity fix will-change: opacity not allow the pointer / click events, I decided to just calculate that the rgb values ββwill be with the desired opacity and hard code in CSS.
I used opacity for disabled buttons and only used a few types of boot buttons for this particular case, so it's not so bad for hacking.
.btn.btn-success[disabled] { opacity: 1; background: rgb(141, 194, 141); } .btn.btn-info[disabled] { opacity: 1; background: rgb(120, 187, 206); }
source share