I found that the input checkbox of suitecrm 8 will be significantly slower if there are more than 30 pieces of data

👨‍💻 Development Help
1

When I click the checkbox to select it, I need to wait 0.5~1 second. The more data I have, the more time I have to wait.

I still don’t understand whether it is an angular problem, a code logic problem, or a performance problem caused by rebuilding?

Have any developers encountered the whole problem?

Attached gif:
b30vp-hqklz

2

When I have 1600 records, it takes 3 seconds, which is very long

3

The entire page is slow, and there is a lag when I click on batch operations.

4

If you open your browser’s Dev tools, network tab, do you see any network action when you click the check boxes?

And do you get any JavaScript errors?

5

I have the same problem. I don’t know when it appeared; it seems like it happened on its own, without any changes. Console error:
/#/accounts/index?return_module=Accounts&return_action=DetailView:1 Blocked aria-hidden on an element because its descendant retained focus. The focus must not be hidden from assistive technology users. Avoid using aria-hidden on a focused element or its ancestor. Consider using the inert attribute instead, which will also prevent focus. For more details, see the aria-hidden section of the WAI-ARIA specification at Accessible Rich Internet Applications (WAI-ARIA) 1.3.
Element with focus: input
Ancestor with aria-hidden: <input type=​"checkbox" aria-hidden=​"true">​

6

Can you get a larger chunk of the HTML surrounding that and post it here? It helps to go
look for the place were it is generated.

7

This error is present even on the SuiteCRM demo page: Screenshot by Lightshot

8

Do you think this problem causes the speed of clicking the checkbox to be slow?

9

This problem is already fixed in v8.8

10

I don’t want to upgrade the minor version. Can you send me the fix commit? I can’t find it.

11

I’m sorry, I can’t find it either.

Maybe you can ask here

12

Since Matt is telling you it’s not easy to get the fix without upgrading, can you tell us why you don’t want to upgrade? For me 8.8 is a very interesting version, lots of good reasons to upgrade.

Have you been having problems with this upgrade, or others?

13

The upgrade has been successful, thank you for your reminder

1 Like
14

Awesome! Was it easy to upgrade to v8.8? Did you find v8.8 more better than previous versions?

16

I haven’t experienced all the new features/fixes yet, but because I have a lot of custom code, the upgrade is not particularly smooth. But it can solve the front-end performance problem, which is important after all. Look at your needs, I still recommend upgrading to v8.8