-
Notifications
You must be signed in to change notification settings - Fork 382
AMP mode and plugin/theme versions need to be included in validated environment setting to determine whether stale #3474
Copy link
Copy link
Labels
ChangeloggedWhether the issue/PR has been added to release notes.Whether the issue/PR has been added to release notes.P1Medium priorityMedium priorityValidationWS:CoreWork stream for Plugin coreWork stream for Plugin core
Milestone
Description
Bug Description
If you switch AMP mode, the validation cache is not invalidated. However, some validation results depend on whether the AMP page is the canonical URL, and therefore change between modes.
An example of this would be the change introduced in #3346, where a change from Transitional to Standard should change the excessive CSS validation errors from New - Accepted to New - Rejected.
Expected Behaviour
When I switch the AMP mode, I expect the changes in validation to be immediately reflected.
Steps to reproduce
- Set mode to
Transitional. - Add enough CSS to the page to hit the excessive CSS validation error on the AMP url of a page.
- The validation screen will show that the excessive CSS validation error is marked as
New - Accepted. - Change mode to
Standard. - The validation screen for that same page will still show the excessive CSS validation error marked as
New - Accepted- it should beNew - Rejectedinstead.
Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance criteria
Implementation brief
QA testing instructions
Demo
Changelog entry
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
ChangeloggedWhether the issue/PR has been added to release notes.Whether the issue/PR has been added to release notes.P1Medium priorityMedium priorityValidationWS:CoreWork stream for Plugin coreWork stream for Plugin core