logical locations to array

Hello, TC,

Twice in the last two weeks, we’ve received two request internally at Microsoft to provide multiple logical locations for a result. Here’s a clear example of why this is useful: an internal accessibility checker is reporting results against a rendered HTML page. It is helpful in their scenario to provide a logical location that is the CSS selector for the problematic item (because this tends to be where the fix is applied) as well as the XHTML xpath to the target item (which they have found is more useful for result matching).

A second team independently raised this suggestion for a second project (that analyzes JSON data).

We have a narrow window to update the spec (today, basically). Would people be open to converting `location.logicalLocation` (a single logical location) to `location.logicalLocations` (an array of them)?

So far, we have only accepted editorial and bug fix changes, as well as one small improvement Jim suggested (adding new roles) that is entirely non-breaking. This change is breaking. It can easily be rendered as non-breaking in the C# SDK (we just need to add a helper for location.logicalLocation that retrieves the 0^th element of location.logicalLocations). And so I’m willing to take it.

Just wanted to take everyone’s pulse on this.

Michael

sarif message