In particular any eyedropper implementation should not allow a web page to "screen scrape" information the user didn't intend to share with the web application, for example, while the user moves the mouse around the screen.
PowerPoint, have eyedropper functionality but are unable to carry it over the web.Įven though some browsers have built-in eyedropper functionality into color input tags, this limits customizability and can be seen as being out of place for many applications. Several creative applications would like to utilize the ability to pick a color from pixels on the screen. This explainer proposes an API that enables developers to use a browser-supplied eyedropper in the construction of custom color pickers. Current version: EyeDropper API ExplainerĬurrently on the web, creative application developers are unable to implement an eyedropper, a tool that allows users to select a color from the pixels on their screen, including the pixels rendered outside of the web page requesting the color data.Current venue: W3C Web Incubator Community Group | WICG/eyedropper-api |.
As the solutions to problems described in this document progress along the standards-track, we will retain this document as an archive and use this section to keep the community up-to-date with the most current standards venue and content location of future work and discussions. This document is intended as a starting point for engaging the community and standards bodies in developing collaborative solutions fit for standardization. Authors: Sidhika Tripathee, McKinna Estridge, Sammy Hannat Status of this Document