Frontmatter
| id | 4892 |
| title | component.Base: getDomRect() => regression bug for arrays |
| state | Closed |
| labels | bug |
| assignees | ExtAnimal |
| createdAt | Sep 11, 2023, 10:44 PM |
| updatedAt | Oct 2, 2023, 11:34 AM |
| githubUrl | https://github.com/neomjs/neo/issues/4892 |
| author | tobiu |
| commentsCount | 1 |
| parentIssue | null |
| subIssues | [] |
| subIssuesCompleted | 0 |
| subIssuesTotal | 0 |
| blockedBy | [] |
| blocking | [] |
| closedAt | Oct 2, 2023, 11:34 AM |

inside the old version, we were able to pass either an id, or an array of ids => getting an array of rects back.
/** * Convenience shortcut * @param {String[]|String} id=this.id * @param {String} appName=this.appName * @returns {Promise<*>} */ getDomRect(id=this.id, appName=this.appName) { return Neo.main.DomAccess.getBoundingClientRect({appName, id}) }the new version assumes that there will be just one rect, transforming it to a DOMRect => this breaks a lot of use cases. E.g.: horizontal scrolling inside
component.DateSelector: https://github.com/neomjs/neo/blob/dev/src/component/DateSelector.mjs#L428