Open dbolack-ab opened 2 weeks ago
This does NOT fix the reported issue; checking the reproduction text in the deployment shows that the issue still exists. I believe the issue reporter made a typo when suggesting the correction, instead of
.page .descriptive.wide {
, they should have entered.page .descriptive.wide + * {
.Current behaviour in Production:
Current behaviour in Test Deployment:
Behaviour with suggested change:
Fixed. Not sure why it looked right before but it definitely did not on reload today.
Uses suggested fix from Issue
Uses more more direct target rather than rearrange the file.
Solves #2688