Basic <select> option from web on jweb crashes Max Application

Javascriptbugs/issuesadvancedbeginner
F S's icon

F S

Hi there,

I have a simpler select option dropdown HTLM element from a site on jweb. But the Max Application crashes when the dropdown menu is clicked on some of the PCs. Can someone please let me know if there is a way to fix it? The app is built for Windows.

Thanks!

Florian Demmer's icon

Florian Demmer

The crash is obviously not ideal and we'll file a ticket internally. In the meantime, can you ensure that you are using onscreen as the rendermode for the jweb object? Does it work then?

F S's icon

F S

Yes based on few reading from the forum, we tried with onscreen and it worked okay! We are still testing on multiple machines. There are follow up questions:

  1. Can you please let us know what onscreen rendermode really does? How is it different from offscreen ?

  2. Is there a reason foroffscreen having a crash for select HTML elements whereas onscreen works fine? Are there other elements on HTMLs or issues with offscreen we should be aware of?

  3. As you said the crash is not ideal! Thanks for taking the step to report! Any error inside the jweb should not crash the app and gives the client a bad impression. Rather an error log on the Max Runtime would be more appreciated.

  4. Following up on #3, is there a way on the client-side to have an equivalent of try-catch on the patch so it doesn't crash the app (considering issue as such will take time to fix)?

  5. Looking at the doc, I believe there is a typo for option #2 in the first paragraph which calls it onscreen with transparent background . I think it's offscreen ...

    Thanks for the reply! Appreciate it.

Florian Demmer's icon

Florian Demmer

Hi FS.

To follow up here, I can't reproduce the issue with Max 8.6.2 on macOS and we had addressed this in Would you mind sharing the version of Max and some insight on your platform and OS version? Also a small example path pointing to a website on which you experience the crash would be great.

If you prefer to share that info in private, please feel free to get in touch with support and refer to this thread.

To answer your other questions.

  1. With off-screen rendering, the Chromium Embedding Framework (CEF) which is used for the in application broawser technology renders to a bitmap and requires the hosting application to register and implement many features for a complete browser experience of popup windows, keyboard focus etc. This is not as robust as the on-screen rendering model where CEF will handle all of that work. The main advantage of using offscreen is for integration of web sites with other Max object overlaid on top of them, but otherwise onscreen rendering will be more efficient and more robust.

  2. There was a bug in earlier Max versions on how we handled <select> elements when using offscreen rendering that according to my testing and knowledge was that has since been addressed.

  3. If the issue persists for you, it might be a regression but as mentioned above having more info about the versions at play and the website leading to crash would be really helpful to get to the bottom of this.

  4. There isn't really a way to try / catch the whole jweb integration and process. However, we are using jweb in Max itself for certain features and are very interested and invested to have a stable CEF integration.

  5. Thanks. We'll make sure to address that.

Hope that helps clearing up some of the things!

Thanks,
Florian