Closed Bug 1997613 Opened 2 months ago Closed 2 months ago

Null pointer dereference when calling DETAILS_FOR anchor does not have accessible

Categories

(Core :: Disability Access APIs, defect, P3)

defect

Tracking

()

RESOLVED FIXED
146 Branch
Tracking Status
firefox-esr115 --- unaffected
firefox-esr140 --- unaffected
firefox144 --- unaffected
firefox145 --- wontfix
firefox146 --- fixed

People

(Reporter: eeejay, Assigned: eeejay)

References

(Regression)

Details

(Keywords: crash, regression)

Crash Data

Attachments

(1 file)

This will crash:

addAccessibleTask(
  `
  <style>
  #btn1 {
    anchor-name: --btn1;
  }

  #target1 {
    position: absolute;
    position-anchor: --btn1;
    left: anchor(right);
    bottom: anchor(top);
  }
  </style>

  <div id="target1">World</div>
  <button id="btn1" aria-hidden="true">Hello</button>
  `,
  async function testARIAHiddenAnchorsAndPosition(browser, docAcc) {
    info("ARIA hidden anchor");
    const target1 = findAccessibleChildByID(docAcc, "target1");
    await testCachedRelation(target1, RELATION_DETAILS_FOR, []);
  },
  { chrome: true }
);
Crash Signature: [@ mozilla::a11y::LocalAccessible::GetAnchorPositionTargetDetailsRelation]
Keywords: crash, regression
Regressed by: 1909354
Attachment #9523857 - Attachment description: Bug 1997613 - Check if anchor actually has accessible. r?morgan → Bug 1997613 - Check if anchor actually has accessible. r?Jamie
Status: NEW → RESOLVED
Closed: 2 months ago
Resolution: --- → FIXED
Target Milestone: --- → 146 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: