1494804 - [Flexbox Inspector][Color Picker] The user can not change the color using the dropper

Status: RESOLVED DUPLICATE of bug 1497312

(DevTools :: Inspector, defect, P3)

Description

[Paul_B]

Attachment: Short video of the issue

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:64.0) Gecko/20100101 Firefox/64.0
Build ID: 20180927100044

STR:

1. Launch Firefox and navigate to a random page (e.g. nytimes.com)
2. Enable the element inspector.
3. Choose a Flex Container or Item.
4. Navigate to the Felexbox Inspector section and select the color picker.
5. Select the small dropper icon.
6. Navigate through the web page and select a color.
7. Observe the Flexbox Container/Item color picker icon.

Actual result:

The color selected using the dropper is not persistent. 
The color picker icon displays only for a very brief moment the selected color and defaults back to the original one. 
I have attached a short video for better understanding.

Expected result:

The user can choose a new color for the highlighter using the dropper in the color picker window and this color is persistent at least for the selected flex-container/item.

Comment 2

[Paul_B]

Hi Gabriel,
In my opinion, these 2 reports address different issues. 
The dropper does not pick up the color that the user selects from the page, while if the user changes colors from the other available options, the color is applied, but only if the highlighter is disabled and re-enabled (on a subsequent flex selection the color goes back to default, so the selection does not persist ).

Comment 3

[Gabriel Luong [:gl] (ΦωΦ)]

(In reply to Paul_B from comment #2)
> Hi Gabriel,
> In my opinion, these 2 reports address different issues. 
> The dropper does not pick up the color that the user selects from the page,
> while if the user changes colors from the other available options, the color
> is applied, but only if the highlighter is disabled and re-enabled (on a
> subsequent flex selection the color goes back to default, so the selection
> does not persist ).

Yes, unfortunately, the fix is also just a single patch. So, I have basically just added the extra scoping in the title of the other since we wouldn't attach the same patch to 2 different bugs.