New
#10
Sad to see such a useful feature being replaced with something more complex and useless!
I think the Chrome Devs just want to p*ss around with new ideas!
The top reasons for abandoning the experiment:
Reason:
Potential dataloss risk/behavioral complexity having an actionable surface so close to a tab close button.
Solution:
Enable hiding of close buttons, everybody knows you can close a tab with a wheel-click.
Reason:
Confusing interactions with mute-whole-site capabilities.
Solution:
Leave site muting in the Site Exceptions list only.
Reason:
Code complexity.
Solution:
Suck it up! To enable/disable a feature with a quick switch of a flag, can't be that complex!!!