Assess the reference to the mousedown event in the base class for render element plugins

Created on 1 May 2018, over 6 years ago
Updated 27 June 2024, 5 months ago

A new WCAG 2.1 Success Criterion, "2.5.2 Pointer cancellation" recommends tying custom behaviours to the up pointer events, in preference to the down events.

Right now there is an event handler binding mousedown in the base class for render element plugins.

This child issue is to assess this case and the impact of making the change if appropriate.

📌 Task
Status

Needs work

Version

11.0 🔥

Component
Ajax 

Last updated about 1 hour ago

Created by

🇦🇷Argentina nico.pinos

Live updates comments and jobs are added and updated live.
  • Accessibility

    It affects the ability of people with disabilities or special needs (such as blindness or color-blindness) to use Drupal.

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • 🇨🇦Canada mgifford Ottawa, Ontario

    Tagging

  • 🇮🇳India ashetkar

    I am adding for patch below version and we faced accessibility issues using mousedown event. If we add mouse up event issue is getting resolved.

    Drupal version : 10.1.8

  • 🇨🇦Canada nord102

    I applied the patch from #5, but I noticed that it caused file uploads to not work as expected because file/file.js was still trying to trigger and act on mousedown.

    I have updated the patch from #5 to include changing mousedown to mouseup for file/file.js as well.

Production build 0.71.5 2024