Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 320664

Summary:	[block selection] Block Selection mode breaks Template variable edit fields
Product:	[Eclipse Project] Platform	Reporter:	Jeremy Flicker <jflicke>
Component:	Text	Assignee:	Tom Hofmann <eclipse>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	daniel_megert, jwsnyder
Version:	3.6
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:	stalebug

Description Jeremy Flicker

2010-07-22 16:16:52 EDT

Build Identifier: Build id: I20100608-0911

With block selection mode enabled, there is an error with the edit fields that appear in a source code editor after you insert a Template containing substitution variables.  When you type into those edit fields, the caret position jumps to the first line of the document after you type the second character.

Reproducible: Always

Steps to Reproduce:
1.Enable block selection mode in the Java Editor
2.Insert a template that contains substitution variables, for example 'if'
3.Type values into the edit field, after the first character, the caret jumps to top line of the editor

Comment 1 Dani Megert

2010-07-23 01:50:04 EDT

Tom, can you take a look.

Comment 2 Tom Hofmann

2010-07-23 03:01:03 EDT

Easily reproduced in any file and very ugly. Depending on the complexity of the fix, this could be a 3.6.1 candidate.

Comment 3 Dani Megert

2011-04-12 06:25:15 EDT

Tom, any plans to fix this for 3.7? If so, the fix needs to be in before April 21.

Comment 4 Tom Hofmann

2011-04-13 11:57:30 EDT

Sorry, I do not have time to work on this before Easter.

Comment 5 Dani Megert

2012-03-20 06:48:27 EDT

Tom, please move this back to the inbox if you no longer plan to work on this at all.

Comment 6 Lars Vogel

2019-11-27 07:17:34 EST

This bug hasn't had any activity in quite some time. Maybe the problem got
resolved, was a duplicate of something else, or became less pressing for some
reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it.
The information can be, for example, that the problem still occurs, that you
still want the feature, that more information is needed, or that the bug is
(for whatever reason) no longer relevant.

If the bug is still relevant, please remove the stalebug whiteboard tag.