Closed Bug 1842053 Opened 1 year ago Closed 1 year ago

[ARIA] rowindex and posinset attributes have different values

Categories

(Core :: Disability Access APIs, defect)

Firefox 115
defect

Tracking

()

RESOLVED FIXED
116 Branch
Tracking Status
firefox-esr115 --- wontfix
firefox116 --- fixed
firefox117 --- fixed
firefox118 --- fixed

People

(Reporter: blewis, Unassigned)

References

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/114.0.0.0 Safari/537.36

Steps to reproduce:

  1. with this grid example: https://run.plnkr.co/plunks/fhGqIp8MCVIw628S/
  2. Make sure focus is in the grid and scroll down until some additional rows are scrolled into view.
  3. using the browser tools, view the accessibility tree.
  4. Locate a row in the grid and examine the attributes of the row.

Actual results:

I see rowindex = 16 posinset = 11 and setsize = 18

Expected results:

I expect rowindex and posinset to be the same and reflect the rowindex value.

This may not be an issue as this was filed against the core am to use rowindex only on rows as the method for communicating the row position. (that is remove group position).
https://github.com/w3c/core-aam/issues/184

The Bugbug bot thinks this bug should belong to the 'DevTools::General' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → General
Product: Firefox → DevTools
Component: General → Disability Access APIs
Product: DevTools → Core

I was able to reproduce your issue in Firefox 115.0 on Windows 10 x64, but not in the latest Nightly 117.0a1 and Firefox 116.0 versions under same configuration.
Could you please check if the issue no longer persists for you too in Firefox 116.0? Thanks

Flags: needinfo?(blewis)

This was fixed by bug 1832228 (Firefox 116).

Status: UNCONFIRMED → RESOLVED
Closed: 1 year ago
Depends on: 1832228
Resolution: --- → FIXED
Target Milestone: --- → 116 Branch
Flags: needinfo?(blewis)
You need to log in before you can comment on or make changes to this bug.