Bug 1861362 Comment 6 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
(In reply to Henry Wilkes (they/them) [:henry-x] from comment #4)
> 3. Checkboxes and other widgets will use the system color.
> 4. Focus outline will use the system color.

Just to be clear, I don't think there isn't any RFP-specific mechanism to stop these colors being measured by web content. It is just that I'm not aware of a way for content to measure these. E.g. the `getComputedStyle` of a focused `<input>` will be grey, rather than the visual accent color.

@pierov tried to do this.
Revision 1 by
on 
(In reply to Henry Wilkes (they/them) [:henry-x] from comment #4)
> 3. Checkboxes and other widgets will use the system color.
> 4. Focus outline will use the system color.

Just to be clear, I don't think there isn't any RFP-specific mechanism to stop these colors being measured by web content. It is just that I'm not aware of a way for content to measure these. E.g. the `getComputedStyle().borderColor` of a focused `<input>` will be grey, rather than the visual accent color.

@pierov tried to do this.
Revision 2 by
on 
(In reply to Henry Wilkes (they/them) [:henry-x] from comment #4)
> 3. Checkboxes and other widgets will use the system color.
> 4. Focus outline will use the system color.

Just to be clear, I don't think there is any RFP-specific mechanism to stop these colors being measured by web content. It is just that I'm not aware of a way for content to measure these. E.g. the `getComputedStyle().borderColor` of a focused `<input>` will be grey, rather than the visual accent color.

@pierov tried to do this.

Back to Bug 1861362 Comment 6