- Issue created by @tetatu
- 🇩🇪Germany jurgenhaas Gottmadingen
Hmm, I'm using a pretty similar setup every day and have never seen anything like this.
Firefox 115 is pretty outdated, any reason you can't update to 136?
In my case, I'm using Gin instead of Claro, but the latter is the base theme of the former, so it's still active. Which other themes have you tried when you mention "not with other themes"?
Have you seen this in your setup before 2.0.7 as well, or is this something new?
This Firefox version is March 2025, so it's up to date.
I tried the Drupal base themes in addition and as I mentioned there was no problem. And out of dozens of ECA models, it only happened with one, which is a pretty complex model anyway. I cloned it, hoping that it would resave and the error would go away, but it didn't.
This is the first time it's happened, and it's not even a working model yet, it's just a draft, a drawing in which I outlined the later steps.
I haven't heard of the Gin theme, I just checked it out, it's an admin theme. I need one that I can customize with CSS like Zen used to be, but unfortunately it doesn't have a D10 version.
- 🇩🇪Germany jurgenhaas Gottmadingen
Firefox 115 and Firefox 115 ESR were released on July 4, 2023, see https://en.wikipedia.org/wiki/Firefox_version_history#Firefox_115_throug...
The current version is 136.
And yes, Gin is an admin theme, but so is Claro as well. And bpmn_io uses the admin theme when opening an ECA model for editing or viewing. Of course, you can change CSS for admin themes as well, they do have documentation around on how to do that.
I'm afraid we can't reproduce this issue and until we have a reproducible scenario on the latest versions of everything, we will postpone this as a support request.
Okay, it's understandable if this bug affects only a few people and requires more research. I'll move on to another topic. I don't like Chrome.
Regarding the Firefox version, I've attached a screenshot showing that version 115.21 is 2025
- 🇩🇪Germany jurgenhaas Gottmadingen
Yeah, maybe a batch release, but still 115 came out 2 years ago. And 136 is the latest, so I wonder why you're not just updating and see if that solves your issue.
And it's not an issue that "affects only a few people". It's currently only you who's reporting this. And we're still in the process of analyzing if this is really anything to do with bpmn_io or caused by something else.
So sorry for pointing this out, take it as irrelevant, this problem is not that important. If I knew it only affected me, I wouldn't have sent it.
I use that version of Firefox because I haven't switched to Windwos 10 or 11, I plan to switch to Linux, but I just haven't gotten there yet.
- 🇩🇪Germany jurgenhaas Gottmadingen
No worries, it's all OK. In this case I'd close this issue and we can still re-open it if it becomes more wider spread or you find more evidence that we should do something about the code.
