Closed
Bug 151114
Opened 23 years ago
Closed 23 years ago
Support nsIAccessibleHyperLink in MAI (Mozilla Atk Implementation)
Categories
(Core :: Disability Access APIs, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: yinbolian, Assigned: yinbolian)
References
Details
(Keywords: access)
Attachments
(1 file, 3 obsolete files)
|
13.84 KB,
patch
|
aaronlev
:
review+
jst
:
superreview+
|
Details | Diff | Splinter Review |
| Assignee | ||
Updated•23 years ago
|
| Assignee | ||
Updated•23 years ago
|
QA Contact: dsirnapalli → mindy.liu
| Assignee | ||
Comment 1•23 years ago
|
||
nsIAccessibleHyperLink is different with other nsIAccessibleXXX interfaces in
that is a auxiliary interface for nsIAccessibleHyperText. So a
nsIAccessibleHyperLink instance is not necessarily a nsIAccessible. In face, in
atk atkhyperlink is a GObject while atkhypertext, atkaction, atktext, etc. are
GTypeInterface's.
| Assignee | ||
Comment 2•23 years ago
|
||
Attachment #87497 -
Attachment is obsolete: true
| Assignee | ||
Updated•23 years ago
|
Whiteboard: need r=
Comment 4•23 years ago
|
||
Comment on attachment 88434 [details] [diff] [review]
patch_v2 (move callbacks into C namespace)
>+
>+static gpointer parent_class = NULL;
>+
Is there any possibility to change the name of "parent_class" to
"super_class_AtkHyperlink"?
>+
>+MaiHyperlink::MaiHyperlink(nsIAccessibleHyperLink *aAcc)
>+{
>+ mHyperlink = aAcc;
>+ mMaiAtkHyperlink = NULL;
>+ mURI = (char*)NULL;
>+}
Would it be better if aAcc is changed to aAccHyperLink?
>+ MaiHyperlink::Initialize(mMaiAtkHyperlink, this);
>+
>+ return (AtkHyperlink*)mMaiAtkHyperlink;
If the caller or AtkHyperlink itself can manage the life cycle itself, it is
okay here.
>+
>+ MaiObject *maiObj = maiHyperlink->GetObject(aLinkIndex);
>+ if (!maiObj)
>+ return NULL;
>+
>+ //no need to add ref it, because it is "get" not "ref" ???
>+ return maiObj->GetAtkObject();
>+}
It must be sure this maiObj will be released somewhere when it should be .
Comment 5•23 years ago
|
||
Other parts of this patch is okay from my view.
| Assignee | ||
Comment 6•23 years ago
|
||
Thanks, Gilbert.
The lifecycle of mai object and mai Hyperlink will be controled by maiCache
(later), I will be careful on that, and you are welcome to check it later.
I see your point of variable names, but their usage are all restricted in narrow
scope, so their meaning is clear in the context :).
| Assignee | ||
Comment 7•23 years ago
|
||
comments in bug 151133 hold here
Attachment #88434 -
Attachment is obsolete: true
| Assignee | ||
Comment 8•23 years ago
|
||
make return statement simpler
Attachment #89221 -
Attachment is obsolete: true
Comment 9•23 years ago
|
||
Comment on attachment 89244 [details] [diff] [review]
patch v4
r=aaronl
Attachment #89244 -
Flags: review+
Comment 10•23 years ago
|
||
Comment on attachment 89244 [details] [diff] [review]
patch v4
sr=jst
Attachment #89244 -
Flags: superreview+
| Assignee | ||
Comment 11•23 years ago
|
||
Checked in! Thanks for everyone!
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Whiteboard: need r=
You need to log in
before you can comment on or make changes to this bug.
Description
•