This is closed as fixed and yet is doesn't seem to...
# adobe
a
This is closed as fixed and yet is doesn't seem to be fixed. https://tracker.adobe.com/#/view/CF-4204497 The provided example code in the ticket demonstrates the issue. Is this fixed in the next update maybe? @Mark Takata (Adobe)
m
They never seem to leave comments detailing what/when. The ticket indicates "Fixed In Build: 2021,0,0,328951" which I think is the launch version of CF2021. Update 3 is
2021,0,03,329779
.
Hard to believe that basic bugs like this are so hard for them to fix properly and timely.
a
Good spot on the versions. Yeah - it may be a regression - but I would hope when these things get "fixed" that there is a test case written so regressions would be spotted. It's either a regression or it just was never fixed.
m
I would hope that they have a comprehensive set of tests too. But it's hard to believe this based on the things I've seen. Either way, I didn't mean to imply that this was a regression. I think it was just never fixed.
Mark should be back tomorrow, so hopefully he can poke someone about it.
a
Polite bump for @Mark Takata (Adobe) if he's back in work mode 🌴
m
YO. Sorry. Yes. Back. Mostly. Lots of random things being thrown at me. Lemme scroll up the thread lol.
OK checking with the team. I wanna say I saw this fly across JIRA and it is fixed in update 4 but I'm double checking with the team now. Sorry for the delay in getting back to you Matthew.
m
@Mark Takata (Adobe) What were you able to find on this? It doesn't look like Update 4 has any bug fixes.
m
So, I'm a bit confused here also, I think now that we're splitting updates into security & separate bugs, the naming convention might have to alter also (maybe to something like S4 and B4 for security/bug). S4 did not have this, but I believe B4 does, which should be coming out (not exactly sure when that's dropping).