> For the complete documentation index, see [llms.txt](https://docs.sharinpix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sharinpix.com/documentation/integrations/events/client-side-events-list.md). # Client-side Events List Client-side events are the unsung heroes that bring web pages to life, reacting precisely to user input. They occur from a simple mouse click to a complex drag-and-drop operation. The following SharinPix components can raise client-side events: * The [SharinPix Album component ](broken://spaces/Hhhsz8OAg6xcF0k0DJhg/pages/LWOdV9eWz0NXM3QUjTmP)(which displays images stored at a record level) * The [SharinPix Single Image component ](broken://spaces/Hhhsz8OAg6xcF0k0DJhg/pages/KspOsiej3fTtx6q3PtcI)(which displays an image having a specific tag stored at a record level) * The [SharinPix Search component](broken://spaces/Hhhsz8OAg6xcF0k0DJhg/pages/hoaqhCz87wLZu1pyTMFv) (which displays images searched across different records) Each has its own set of events. ## Album Component events * **image-new** – when an image is uploaded * **images-selected** – when an image check box is checked (or unchecked) * **image-processed** – After the completion of processing a large file. * **image-deleted** – when an image has been deleted * **image-undeleted** – when an image has been undeleted * **image-rotated** – when an image is rotated * **image-cropped** – when an image is cropped * **image-annotated** – when an image is annotated * **tag-image-new** – when a tag is added to an image * **tag-image-deleted** – when a tag is removed from an image * **viewer-image-viewed** – when an image is clicked to be viewed in the large view * **viewer-closed** – when the large view is closed * **image-sort-completed** – when custom sorting has been applied to images * **image-sync-completed** – when an image has been synchronized * **restricted-file-error** - when uploading a restricted file type using the [upload\_accept parameter](/documentation/features/upload-images/restrict-uploads-using-file-extensions.md). ## Single Image Component events * **image-new** – when an image is uploaded * **images-selected** – when an image check box is checked (or unchecked) * **image-processed** – After the completion of processing a large file. * **image-deleted** – when an image has been deleted * **image-undeleted** – when an image has been undeleted * **image-rotated** – when an image is rotated * **image-cropped** – when an image is cropped * **image-annotated** – when an image is annotated * **tag-image-new** – when a tag is added to an image * **tag-image-deleted** – when a tag is removed from an image ## Search Component events * **search-ready** – when the component is opening and fully loaded * **images-selected** – when an image check box is checked (or unchecked) * **viewer-image-viewed** – when an image is clicked to be viewed in the large view * **viewer-closed** – when the large view is closed --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.sharinpix.com/documentation/integrations/events/client-side-events-list.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.