Three years ago, bug #66497 was reported.
This bug hits a basic aspect of Xojo: controls on a webpage fire their opening events before the page’s constructor method fires. To work around this, you have to move code to the controls’ Shown event, which is far from ideal. This approach delays loading until the page is visible, resulting in a jarring user experience with a double reload. If the page is complex enough it can fire after the user startes to enter data.
We haven’t found a way to work around this.
Xojo acknowledged and verified the bug promptly three years ago.
Two years ago, a bot tagged it as “Web,” but no progress was made for on this bug in the 3 years.
The bug has undergone numerous milestone reassignments (Suggesting it meet the criteria to be fixed?):
• 1st milestone reassignment: 2023r2
• 2nd milestone reassignment: 2023r3
• 3rd milestone reassignment: 2023r4 (on then off then on again)
• 4th milestone reassignment: 2024r1
• 5th milestone reassignment: 2024r2
• 6th milestone reassignment: 2024r3
• 7th milestone reassignment: 2024r4
• 8th milestone reassignment: 2025r1
5 posts - 2 participants