Actually, both were addressed in ZC 1.5.5 (not saying specifically 1.5.5 versus 1.5.5a, but at least in that "series").
A/the solution was identified back in the middle to end of 2014 before ZC 1.5.4 was officially released. Then it was not incorporated in ZC 1.5.4, but was referenced as a bug in ZC 1.5.4 (but also backwards to other versions of ZC), which means that "officially" it wouldn't make it into the released core until the next version, dated change, or other release. In this case ZC 1.5.5ish. For me and why I couldn't recall the specifics was the pre-ZC 1.5.4 discovery and correction that didn't make it into ZC 1.5.4, but having both encountered the issue and taken part in testing of it against ZC 1.5.1, 1.5.3, and 1.5.4, well forgot the incorporation date/version, but remembered to which/where it related.
So, I'm not sure to which sessions "correction" you are referring, but of the solutions posted and existing code, I'm not visually seeing a difference in the "resolution". Maybe I need new eyes or a bigger screen.
Bookmarks