Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - tteredaget

#1
Quote from: Ruokoton on July 09, 2024, 12:27:31Starting yesterday(?) the location search fields in the web planner have been broken. The behaviour is the same using Firefox, Chrome (both on MacOS and Linux) and Android version of Chrome. Search itself works ok, but if you select any of the found items, the field just goes blank and the following error can be seen in the browser console:
 TypeError: Cannot read properties of undefined (reading 'id')
    at t.selectSuggestion (main.66dc84f892ee88c0.js:3:981659)
    at main.66dc84f892ee88c0.js:3:979133
    at fx (main.66dc84f892ee88c0.js:3:2180731)
    at Object.g [as next] (main.66dc84f892ee88c0.js:3:2180898)
    at pe.next (main.66dc84f892ee88c0.js:3:2080627)
    at me._next (main.66dc84f892ee88c0.js:3:2080296)
    at me.next (main.66dc84f892ee88c0.js:3:2079982)
    at main.66dc84f892ee88c0.js:3:2077923
    at D (main.66dc84f892ee88c0.js:3:2097238)
    at Qp.next (main.66dc84f892ee88c0.js:3:2077762)
    at Qp.emit (main.66dc84f892ee88c0.js:3:2150929)
    at t._emitSelectionChangeEvent (main.66dc84f892ee88c0.js:3:408040)
    at t._selectViaInteraction (main.66dc84f892ee88c0.js:3:407634)
    at main.66dc84f892ee88c0.js:3:408724
    at fx (main.66dc84f892ee88c0.js:3:2180731)
    at g (main.66dc84f892ee88c0.js:3:2180898)
    at HTMLElement.<anonymous> (main.66dc84f892ee88c0.js:3:40813)
    at h.invokeTask (polyfills.716d9c308f3b03db.js:1:8596)
    at Object.onInvokeTask (main.66dc84f892ee88c0.js:3:2153061)
    at h.invokeTask (polyfills.716d9c308f3b03db.js:1:8517)
    at h.runTask (polyfills.716d9c308f3b03db.js:1:3623)
    at h.invokeTask [as invoke] (polyfills.716d9c308f3b03db.js:1:9729)
    at O (polyfills.716d9c308f3b03db.js:1:23294)
    at N (polyfills.716d9c308f3b03db.js:1:23667)
    at HTMLElement.G (polyfills.716d9c308f3b03db.js:1:23850)


I don't see this error. It seems it has been fixed.