Closed Bug 1519955 Opened 2 years ago Closed 2 years ago

Remove boxobject usage in accessibility

Categories

(Core :: XUL, enhancement, P3)

enhancement

Tracking

()

RESOLVED FIXED
mozilla67
Tracking Status
firefox67 --- fixed

People

(Reporter: enndeakin, Assigned: enndeakin)

References

Details

Attachments

(1 file)

No description provided.
Priority: -- → P3
Attachment #9036407 - Flags: review?(jteh)
Comment on attachment 9036407 [details] [diff] [review]
Replace boxobjecct calls

Review of attachment 9036407 [details] [diff] [review]:
-----------------------------------------------------------------

::: accessible/xul/XULTreeGridAccessible.cpp
@@ +413,5 @@
> +    return nsIntRect();
> +  }
> +
> +  nsIFrame* bodyFrame = bodyElement->GetPrimaryFrame();
> +  if (bodyFrame) {

Can you explain why we don't return nsIntRect(); if (!bodyFrame) like we do in XULTreeItemAccessibleBase::BoundsInCSSPixels? I guess you could argue potentially unusable coords are better than no coords, but I'm confused by the difference here.

I probably wrote those two bits at different times. I think it should just return nsIntRect() in both cases as the tree is hidden when it has no frame. I will make that change.

Comment on attachment 9036407 [details] [diff] [review]
Replace boxobjecct calls

(In reply to Neil Deakin from comment #2)

> I probably wrote those two bits at different times. I think it should just return nsIntRect() in both cases as the tree is hidden when it has no frame. I will make that change.

Agreed. r+ with that change made.
Attachment #9036407 - Flags: review?(jteh) → review+
Pushed by neil@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/1178c5fddda7
Don't use boxobject properties in accessibility, r=jteh
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla67
You need to log in before you can comment on or make changes to this bug.