This bug has been marked as invalid for gnome-terminal because it is a feature of bash shell.
However, should we mark gnome-terminal as impacted?...
I see the benefit to the change in bash from a security perspective, so perhaps gnome-terminal needs to adapt to this new feature.
Specifically, I think this behavior could be confusing to users:
> If you try to select the highlighted text by clicking
> and dragging the mouse pointer, the text color actually
> inverts, and the text looks like it is not selected,
> when it in fact is selected.
For example, @Egmont Koblinger suggested changing the high-light color in the terminal, so it does not match the "bracketed paste" color. This can be done through the color profile for gnome-terminal. This is one option, but it may have implications for accessibility (people who can not distinguish different colors due to color-blindness).
There may also be other things that gnome-terminal cold do to adapt to this change.
Therefore, may be we should leave gnome-terminal as impacted for now, so a good solution can be devised?
This bug has been marked as invalid for gnome-terminal because it is a feature of bash shell.
However, should we mark gnome-terminal as impacted?...
I see the benefit to the change in bash from a security perspective, so perhaps gnome-terminal needs to adapt to this new feature.
Specifically, I think this behavior could be confusing to users:
> If you try to select the highlighted text by clicking
> and dragging the mouse pointer, the text color actually
> inverts, and the text looks like it is not selected,
> when it in fact is selected.
For example, @Egmont Koblinger suggested changing the high-light color in the terminal, so it does not match the "bracketed paste" color. This can be done through the color profile for gnome-terminal. This is one option, but it may have implications for accessibility (people who can not distinguish different colors due to color-blindness).
There may also be other things that gnome-terminal cold do to adapt to this change.
Therefore, may be we should leave gnome-terminal as impacted for now, so a good solution can be devised?