This looks like an issue we added a ticket for right before christmas (DEF-3061).
We think it is related to a security update for Safari to 11.0.2. Does it look like OK in another web browser, chrome for example?
This looks like an issue we added a ticket for right before christmas (DEF-3061).
We think it is related to a security update for Safari to 11.0.2. Does it look like OK in another web browser, chrome for example?