Skip to content

[Bug] Extension incorrectly returns wrong message when changing from Element to Requirements view when focused #2394

@philljenkins

Description

@philljenkins

Task or scenario I'm trying to do

  • Get a list of issues sorted by Requirement for an element/component and all it's children

Steps to reproduce the behavior:

  1. Go to any page, such as Altoro Mutual
  2. Click on Scan page
  3. Select an element, such as main
  4. Select "Focus Mode" by selecting that button switcher next to All
  5. Notice all the issues listed as usual for main and all the children
  6. Select Filter drop-down and click on Requirements
  7. Incorrectly clears list of issues and returns unexpected error message that the page hasn't been scanned.

Screenshot

Screenshot after step 4, showing the issue with the Extension
Image

Screenshot after step 3, correctly showing all the issues after a scan
Image

Desktop (please complete the following information):

  • OS: MacOS
  • Browser: Chrome

Additional context
Add any other context about the problem here.

  • scenario works correctly with other filter choices, such as Rules
  • scenario may work at time, such as when selecting Filter by Rules first, and then Requirements

Definition of Done

  • NA Design artifacts reviewed
  • Work item implemented
  • Automated test case created (when applicable)
  • Unit test completed
  • Run Checker (when applicable)
  • Manual and Screen Reader Testing (when applicable)
  • Video recording of user experience walkthrough (if impact to UX)
  • PR created

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions