Describe the bug
I've started observing a Maximum call stack size exceeded exception when the year property is set programmatically.
|
year: { |
|
type: Number, |
|
value: new Date().getFullYear(), |
|
notify: true |
|
}, |
|
connectedCallback() { |
|
super.connectedCallback(); |
|
this.addEventListener("selected-date-changed",this._onSelectedDateChanged); |
|
this.addEventListener("year-changed",this._onYearChanged); |
|
} |
|
_onYearChanged(ev) { |
|
if (ev.detail.value) { |
|
this.dispatchEvent(new CustomEvent("year-changed", { |
|
detail: { value: ev.detail.value } |
|
})); |
|
} |
|
} |
Expected behavior
Setting the year property programmatically should not cause a Maximum call stack size exceeded exception. Instead, it should update the value without triggering infinite recursion.
Minimal reproducible example
document.querySelector("fc-year-calendar").year=2024;
Add-on Version
4.3.2-SNAPSHOT
Vaadin Version
24.7.0
Additional information
No response
Describe the bug
I've started observing a
Maximum call stack size exceededexception when the year property is set programmatically.YearMonthCalendarAddon/src/main/resources/META-INF/frontend/fc-year-calendar/fc-year-calendar.js
Lines 82 to 86 in afea23c
YearMonthCalendarAddon/src/main/resources/META-INF/frontend/fc-year-calendar/fc-year-calendar.js
Lines 172 to 176 in afea23c
YearMonthCalendarAddon/src/main/resources/META-INF/frontend/fc-year-calendar/fc-year-calendar.js
Lines 327 to 333 in afea23c
Expected behavior
Setting the year property programmatically should not cause a Maximum call stack size exceeded exception. Instead, it should update the value without triggering infinite recursion.
Minimal reproducible example
Add-on Version
4.3.2-SNAPSHOT
Vaadin Version
24.7.0
Additional information
No response