Closing this bug as the issue cannot be reproduced for 4.8.2. No content associated with this bug needs to be added to or removed from the 4.8 release notes.