You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Kind of goes hand in hand with #1491 really - the disable-element extension for when a request is in flight accepts a CSS selector, but if you used e.g. a class name in that selector you could potentially find multiple target elements.
Use case is, I might want to disable multiple other actions (e.g. buttons) while my request is in flight, not just a single one by ID.
The text was updated successfully, but these errors were encountered:
The needed change should be pretty simple. In the current state, the extension uses querySelector to select the first that matches the selector. Instead querySelectorAll could be used like this:
Kind of goes hand in hand with #1491 really - the
disable-element
extension for when a request is in flight accepts a CSS selector, but if you used e.g. a class name in that selector you could potentially find multiple target elements.Use case is, I might want to disable multiple other actions (e.g. buttons) while my request is in flight, not just a single one by ID.
The text was updated successfully, but these errors were encountered: