Closed
Bug 185847
Opened 23 years ago
Closed 22 years ago
Active Accessibility: get screen coordinates for word, both clipped and unclipped
Categories
(Core :: Disability Access APIs, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: aaronlev, Assigned: aaronlev)
Details
(Keywords: access, topembed)
A screen magnification software vendor has asked to be able to get the screen
coordinates for a specific word, as opposed to the coordinates for an entire
node which may contain many words.
They want to know both the unclipped rectangle, and the rectangle clipped by the
window edge.
We'll probably have to put this on ISimpleDOMNode, or perhaps devise a new
interface for this and bug 185846.
| Assignee | ||
Comment 1•22 years ago
|
||
Kyle, in GetCharacterExtents(), why do you use CreateRenderingContext() and
SetFont(), etc. rather than use nsIWidget::GetRenderingContext()? Is it more
correct?
Hi Aaron,
Is there anything wrong with that codes?
I thought the function "nsIWidget::GetRenderingContext()" also creates a rc object,
see the following link for details.
http://lxr.mozilla.org/seamonkey/source/widget/src/xpwidgets/nsBaseWidget.cpp#571
and we also need a call of SetFont() after that.
| Assignee | ||
Comment 4•22 years ago
|
||
Okay Simford. Sorry for the "false alarm".
| Assignee | ||
Comment 5•22 years ago
|
||
checked in as part of bug 185846
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•