Xojo Web Bug Bash 2022

WebSegmentedButton - Pressed event fired only once
WebSegmentedButton - Pressed event fired only once (#62176) · Issues · Xojo Inc / Xojo · GitLab

1 Like

Would be great to get the WebPagination component into a usable state by fixing these two bugs:

https://tracker.xojo.com/xojoinc/xojo/-/issues/68578
https://tracker.xojo.com/xojoinc/xojo/-/issues/68579

1 Like

Those 2 are not nominated yet for the Bug Bash. Do you have any more nominations left? You just need to add a comment with the text [BugBash2022Nominee]

1 Like

Thank you @AlbertoD for the reminder, it is done now. :+1:

2 Likes

Hi @Ricardo_Cruz , a small question. With yesterday’s fix (#65196) 3 more cases named for the [BugBash2022Nominee] were closed (but not yet tagged). Can my votes on those 3 cases be reassigned since they were caused by the same problem or not?

My guess is that you can remove the nomination (because it was a duplicate case) and assign each one to another case.

1 Like

I think Alberto is right. Let me double check it anyway.

2 Likes

Yes @Attilio_Punzi, no need to remove anything. In this case you can nominate a few more as your tickets didn’t even saw the bug bash label.

2 Likes

Each time I try to give web 2 a chance, I got lots of silly bugs that should not be there in a tool :expressionless:

Another for the collection.

https://tracker.xojo.com/xojoinc/xojo/-/issues/69614

This is really BASIC user interaction and is not working as expected :expressionless:

https://tracker.xojo.com/xojoinc/xojo/-/issues/69616

Thanks for opening the cases @Ivan_Tellez :ok_hand:

Working on web 2 still feels like a beta :expressionless:

https://tracker.xojo.com/xojoinc/xojo/-/issues/69620

Please bring back autosave!
And this one is very annoying:
https://tracker.xojo.com/xojoinc/xojo/-/issues/68754

Just a couple hours moking up something simple and bugs keep poping out.

BUG WebTooltips are not removed when the parent control does
https://tracker.xojo.com/xojoinc/xojo/-/issues/69625

BUG in WebControl, The CLOSE method is suposed to do nothing?:
https://tracker.xojo.com/xojoinc/xojo/-/issues/69626
In web 1.0 this method does nothing so, maybe the docs are right?

https://documentation.xojo.com/api/user_interface/web/webcontrol.html#webcontrol-close

@Ricardo_Cruz, can you confirm how to create a Control Set in Web 2.0? Documentation also states there: “if the control is part of a Control Set…”

Edit: Same thing on WebUIControl…

That’s a documentation bug, there are no control sets. Thanks for pointing it out.

You can create and remove controls at runtime, calling AddControl on web views (WebPage, WebContainer, WebDialog, WebRectangle, …).

Calling Close will definitely remove the control from the view.

@Ulrich_Bogun the way to nominate cases is adding [BugBash2022Nominee] as a comment in the issue.

BUG Websearchfield loses text when placed on a container and the command Container.Visible=true is executed
https://tracker.xojo.com/xojoinc/xojo/-/issues/69619

1 Like

is there any tutorial on how to add them and manage their events? Is there a way to have a single event handler for many controls like when a Control Set was used on web 1?

While this is a Desktop article, it’s pretty much the same in Web projects:

Using AddHandler you can forward the events of several controls into a single method.