Our powerful JS Calendar component


Post by kinetic »

We are experiencing an issue where the page using Bryntum Calendar (as scheduler) does not load (for a small number of users) in Chrome browser (varying versions). The problem does not happen in Incognito mode, or in any other browser we have tried. 1 user reports it has always been an issue, 1 or 2 other users are now beginning to see the same case.

We are customizing the date header in the Bryntum Calendar with Fluent UI components. 1 of 3 components are rendered, depending on the chosen view (toolbar buttons).

We can’t be certain whether the error is caused by the calendar, the browser, Fluent UI, React, or some combination of all factors based on how we are using them! We can’t really set this up to reproduce and show you, but wondered if you had encountered a similar error before? We will also pose the question to the teams at Fluent / Google.

Please find enclosed images of:
• the console error
• fluent nodemodules file where the error originates
• the React component file mentioned in the stack trace
• list of dependency versions used in the project

Attachments
context is undefined.png
context is undefined.png (125.6 KiB) Viewed 173 times
Console error.png
Console error.png (27.94 KiB) Viewed 173 times
Component example.png
Component example.png (8.83 KiB) Viewed 173 times

Post by kinetic »

The rest of the attachements....

Attachments
customizablejs.png
customizablejs.png (191.91 KiB) Viewed 172 times
Dependency versions.png
Dependency versions.png (16.05 KiB) Viewed 172 times
DateHeaders.png
DateHeaders.png (65.99 KiB) Viewed 172 times

Post by ghulam.ghous »

Hi @kinetic,

We do not have encountered this issue before and as you have already mentioned, we couldn't reproduce it in our online demos as well. But I believe what you can try here is, start emitting the possible factors that can cause this issue. Probably it is related to some chrome extensions maybe. Because such issues can happen due to some extensions. If it could have been an issue on our end, it could have been faced by all the users. So probably there's something wrong on the customer end with their browser as it works for them in the incognito mode. Hope you guys get it all figured out!

Regards,
Ghous


Post by kinetic »

Thanks Ghous!

Eventually we have traced it to react-dom, it was related to over-riding the library for working locally, so while a little inconvient is thankfully not a show-stopper. Very strange!


Post by ghulam.ghous »

Hi Kinetic,

Glad you have figured it out. Please don't hesitate to reach out to us if you need any further assistance related to our product.

Regards,
Ghous


Post by kinetic »

Thank you!
I actually do have a question relating to filtered out event cards that are still showing a little bit...I will create a new post :)


Post Reply