Closed Bug 535074 Opened 15 years ago Closed 14 years ago

Be able to scale text size with correct cursor placement

Categories

(Skywriter Graveyard :: Editor, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: brettz9, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.6) Gecko/20091201 Firefox/3.5.6 (.NET CLR 3.5.30729)
Build Identifier: 

Hi,

I noticed that in Bespin, when one resizes the (canvas) text via control+, the cursor position does not adjust correctly along with the resized text.

It would be great if one could use control+/- to resize the text and still have it work, as some of us like our IDEs to have larger (or smaller?) font sizes.

Thanks!

Reproducible: Always

Actual Results:  
Cursor is off position

Expected Results:  
Cursor aligns correctly along with the resized text
Does this bug have any relation to bug 487920 or bug 533631?

And, just for confirmation, is this still an issue in the latest version of Bespin (currently 0.6.2)?
Component: General → Editor
OS: Windows Vista → All
QA Contact: general → editor
Hardware: x86 → All
I'm sorry but I don't have much time now to confirm. If I've made the bug clear (just change the text size of the page, e.g., via control + or control -), it should be obvious to notice whether the cursor is aligned. Before, if you keep increasing the text size, the cursor would move farther and farther away from the current line (very obvious). Thanks...
And, it might relate to the other bugs you mentioned, I'm not sure. I don't remember now if the misalignment was vertical or horizontal or both. Thanks.
I have now confirmed, and it is working at least as of 0.6.2 Drop-in...Nice work! (Btw, should I change the status to fixed or worksforme?)
Marking as RESOLVED WORKSFORME per comment 4, since this bug was never confirmed before it was fixed.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.