fix: lion-calendar: when determining if user interacted with a day button we no longer examine event.target but event.composedPath()[0] since it otherwise fails in Firefox 111+

This commit is contained in:
Danny Moerkerke 2023-04-19 15:17:14 +02:00 committed by gerjanvangeest
parent 5b8d655f10
commit 12f1800806
3 changed files with 7 additions and 2 deletions

View file

@ -0,0 +1,5 @@
---
'@lion/ui': patch
---
lion-calendar: when determining if user interacted with a day button we no longer examine event.target but event.composedPath()[0] since it otherwise fails in Firefox 111+

2
package-lock.json generated
View file

@ -22334,7 +22334,7 @@
},
"packages/ui": {
"name": "@lion/ui",
"version": "0.1.5",
"version": "0.2.0",
"license": "MIT",
"dependencies": {
"@bundled-es-modules/message-format": "^6.0.4",

View file

@ -753,7 +753,7 @@ export class LionCalendar extends LocalizeMixin(LitElement) {
const isDayButton = /** @param {HTMLElement} el */ el =>
el.classList.contains('calendar__day-button');
const el = /** @type {HTMLElement & { date: Date }} */ (ev.target);
const el = /** @type {HTMLElement & { date: Date }} */ (ev.composedPath()[0]);
if (isDayButton(el)) {
this.__dateSelectedByUser(el.date);
}