Just downloaded and started using 2025r3.
First thing I notice: the shown event is never fired on dynamically placed WebContainer Controls. Seems I need to move everything to Opening?!?
Is this intentional or a bug?
Just downloaded and started using 2025r3.
First thing I notice: the shown event is never fired on dynamically placed WebContainer Controls. Seems I need to move everything to Opening?!?
Is this intentional or a bug?
Sounds like a bug.
Can you make a small example?
Verify it worked in 2025r2 and fails in 2025r3. Then it’s a regression and we have a chance it gets fixed in r3.1 quickly.
I never used 2025r2 because of https://tracker.xojo.com/xojoinc/xojo/-/issues/79699
This is so basic, bizar nobody noticed this during testing. Apparently nobody is using Web in the betatesters group…
Created a new issue:
Since the Opening Event is being fired, I have a workaround it seems, but it will take some time migrating all the Shown to Opening; and that may cause new issues with how things are displayed…
There is a big difference between opening and shown.
Opening runs before the controls are sent to the browser, so you can define the initial look.
Shown runs later, after the controls are delivered and visible in the browser.
I can confirm, that this used to work in 2025r2, but fails in 2025r3.
@Ricardo_Cruz
I know; afraid as long as this isn’t being fixed, 2025R3 will be unusable for me as well. Need to stick to 2025R1.1 still… And since @Anthony_G_Cyphers will be migrating to Libraries for it’s new GraffitiSuite release, things are only getting worse.
We would hope for a 3.1 to fix this.
As Pro you should have access to the betas.
I do have access, however I lack the time to test my code against the beta’s…
With Web2 they tried to make Opening event work better than in Web1.
Code that needed to be in Shown event with Web1 now can be used in Opening event (maybe not all).
Other people testing the betas may not have much code in Shown event or not use the WebContainer controls dynamically.
Too bad that you found a bug that is a showstopper for you just by downloading 2025r3 and spending a few minutes with it.
I invite you to try to spend some time within the beta cycle to find this type of bugs before they finalize the changes before shipping.
I hope Ricardo can fix this for version 3.1.
Unfortunately I use some ExecuteJavascript in the Shown Event here and there, that does not behave well when being transferred to the Opening Event.
I certainly hope this will be fixed in 3.1