Initial testing shows that this has been resolved. Please report in Community Feedback (No Product Questions) if you are still seeing this issue.