On April 23, 2019, Google promoted Chrome version 74.0.3729.108 to its stable channel, which would have users automatically updated to this version at an unspecified time in the following weeks. This update brought with it unexpected behavior with the output viewing experience for Reverb and Reverb 2.0 Formats stored on the local file system. Basically, when you try to view output for a documentation set that was created with more than one group in ePublisher, the output will fail to load any of the groups past the first, giving the experience of an incomplete help set. This behavior is not present when the output is hosted on a web server, but it is a cause for concern because on first look there seems to be an error with either Reverb, Reverb 2.0, or the source documents.
Upon further inspection, we were able to determine that the behavior that caused this loading error in Reverb and Reverb 2.0 was due to a bug that was part of the 74.0.3729.108 release of Google Chrome. We were able to create a minimal test case that was independent of our outputs to show Chromium the exact issue that occurred, in order to give some direct and useful feedback, and possibly get a resolution to the issue for our outputs. We are still in direct contact with Chromium regarding this case in order to determine the best strategy to take on our outputs to provide the best experience for ePublisher users’ audiences in the future.
As of today, May 30, 2019, the resolution from Chromium is still inconclusive but we have been proactive and developed a new, future-proof way to give the full experience back to Reverb 2.0. This fix is provided in ePublisher 2019.1, and all users will be able to enjoy the benefits of this fix with no extra effort once Format Version 2019.1 is selected! (provided your project doesn’t contain any .js file overrides, of course) So, rest easy knowing that we’ve worked diligently to provide the best experience possible for Reverb 2.0 in ePublisher 2019.1.