401554 – Message.Editor: Clicking the "=" icon on a key with a duplicate-value-issue does nothing

Bug 401554 - Message.Editor: Clicking the "=" icon on a key with a duplicate-value-issue does nothing

Summary: Message.Editor: Clicking the "=" icon on a key with a duplicate-value-issue d...

Status:	NEW

Alias:	None

Product:	Babel
Classification:	Technology
Component:	Plugins (show other bugs)
Version:	unspecified
Hardware:	PC Windows 8

Importance:	P3 normal (vote)
Target Milestone:	---
Assignee:	Babel Bugzilla inbox
QA Contact:

URL:
Whiteboard:	stalebug
Keywords:

Depends on:
Blocks:

Reported:	2013-02-22 12:20 EST by Clemente Lodi-Fè
Modified:	2023-01-06 18:23 EST (History)
CC List:	0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Clemente Lodi-Fè

2013-02-22 12:20:12 EST

Ported over from eclipselabs

What steps will reproduce the problem?
1. Open a locales file in the message editor
2. create 2 keys
3. fill in the same values for both keys
4. They now should be marked with a "duplicate values"- issue
5 . open one of the keys and click the = icon on the top right corner (see image)

What is the expected output?
A Window should pop up which tells you which keys have the same value as the currently selected key

What do you see instead?
Nothing happens

Note: The original bug report also stated that a NullpointerException was thrown when the "=" icon was clicked. This does not seem to happen anymore

Comment 1 Eclipse Genie

2015-02-13 11:58:52 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.

--
The automated Eclipse Genie.

Comment 2 Eclipse Genie

2017-02-03 09:00:04 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.

--
The automated Eclipse Genie.

Comment 3 Eclipse Genie

2019-01-25 13:01:47 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.

--
The automated Eclipse Genie.

Comment 4 Eclipse Genie

2021-01-15 16:53:13 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.

--
The automated Eclipse Genie.

Comment 5 Eclipse Genie

2023-01-06 18:23:51 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.

--
The automated Eclipse Genie.