980996 - Color picker remains opened when its associated input type color is removed

Status: NEW

(Core :: Widget: Cocoa, defect)

Description

[Arnaud Bienner]

As described in bug 975468:
if an input type color input is deleted (e.g. we close the tab/window) after we click on it, the color picker remains opened.
Even if it's safe, as we can change the color in the color picker or close without crashing or any side effect, it would probably be less confusing to close it when it's associated input is removed IMHO.

Comment 1

[Claude Pache]

I don't think it's a bug, but the expected behaviour on the platform.

For example, open TextEdit; create a new document; open the color picker (⇧⌘C); close the document. The color picker remains in place.

Comment 2

[Arnaud Bienner]

Thanks for your comment :)
As I said, I don't use OS X a lot, so I don't really know what is the expected behavior.
Do you know if the behavior is similar for other native OS X applications? (maybe worth to not check only one application).

If so, we might just close this bug as WONTFIX.

Comment 3

[Claude Pache]

Same behaviour observed in Mail, Pages, BBEdit (colors selectable in some tab of the Preferences), iDefrag Lite (customisable colors of the legend).

For Terminal, where colors can be chosen in the Preferences window, it is more sophisticated. The color picker remains open as long as the Preference window is open, even when a tab is selected where there is no color to be selected. However, the picker is automatically closed as soon as the Preferences window is closed, and is reopened when the Preference window is reopened and the color picker where open the last time the Preference window was closed. (My theory is that this behaviour prevents the user to try to unsucessfully change the colors of Terminal windows directly, for they can only be changed in Preferences.)

Comment 4

[Claude Pache]

However, what should be taken care of, is that the color picker should not act over a hidden color input, for that is confusing (provoking unexpected changes). I've just open bug 981866 for that issue. (Well, perhaps I could have reused this bug?)