Skip to content
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.

Erratic Tab key in Menu Dialog boxes #3639

Closed
openstreetmap-trac opened this issue Jul 23, 2021 · 3 comments
Closed

Erratic Tab key in Menu Dialog boxes #3639

openstreetmap-trac opened this issue Jul 23, 2021 · 3 comments
Assignees
@openstreetmap-trac
Labels
Component: potlatch2 Priority: major Resolution: worksforme Type: defect

Comments

@openstreetmap-trac
Copy link

Reporter: PierZen
[Submitted to the original trac issue database at 4.47pm, Saturday, 2nd April 2011]

In the Menu Window on the left, when opening a new Dialog box and using tab key to move displace the cursor in the various TextFields, various problems arised.

By example, I create a node and select Supermarket in Shopping Group. In the Supermarket Dialog box, I select the Naming Menu Tab on top.

Problem 1 :

If I press the Tab key, the cursor is moved to the Unset Textfield 1 (ie. Name) and the word Unset is erased. If a press the Tab key again without entering any value, the cursor is not moved to the next Textfield and the window is frozen and the following error message arises (French version) :

Error #1023: Il s'est produit un debordement de pile
( Translation : Stack overflow occurred.? ).
at mx.core::UIComponent/get focusManager()

It seems that it is enough to press the Tab key twice to create this error. Also, sometimes, Adobe Flash Player Crashes.

Problem 2 :

If I enter text in Textfield 1 (Name) and use again the Tab key to move to a Unset TextField 2 (ie. International name), different situations arises.

Sometimes, the same problem as for Textfield 1 arises (error 1023).
Sometimes, the cursor is moved to the Unset TextField 2 (ie. word Unset appears in gray). Then, when inserting text, the word Unset is added after the text inserted.

Example : key=addr:street value=OneUnset
@openstreetmap-trac openstreetmap-trac self-assigned this Jul 23, 2021
@openstreetmap-trac
Copy link
Author

Author: PierZen
[Added to the original trac issue at 6.30pm, Monday, 11th April 2011]

#3639: Erratic Tab key in Menu Dialog boxes
-----------------------+----------------------------------------------------
Reporter: PierZen | Owner: potlatch-dev@
Type: defect | Status: new
Priority: major | Milestone:
Component: potlatch2 | Version: 2.0
Keywords: |
-----------------------+----------------------------------------------------
I Filed this ticket two weeks ago but no answer yet. A few days later, I found that problem 1 was fixed, but not problem 2. Here is precisions, tha I hope will help to identify the problem.

Problem 1, fixed : Press the keyboard TAB key to move from one textfield to another.

Problem 2: This problem arises when entering text in a Textfield and then press the keyboard TAB key to move to other Textfields

New tests today at url http://www.openstreetmap.org/edit?editor=potlatch2 :

When entering text in a Textfield, the Potlatch2 API does not react the same way, if I use the mouse or the keyboard TAB key to move to the next Textfield. Plus, doing repetitively the same test, different situations may arise.

For example, after we enter text in a Textfield,

  1. If we use the mouse and click in the next Textfield, the cursor is moved to the
    next Textfield, the word Unset is erased and the text entered is passed correctly
    to the key value.

2 If instead we press the keyboard TAB key, the cursor is moved to the next
Textfield, but this time the word Unset is not erased in this new Textfield.
If we enter text and press the keyboard TAB key again,

  1. Sometimes the menu is moved to a new Tab Dialog Box and text added.
    For example, when being in the 'Address' Tab Dialog Box, It happens many
    times that the API jumped to the 'Name' Tab Dialog Box with registering
    source=Bing while I had entered an other key and value in an other Dialog Box.
  2. Sometimes, the cursor is not moved and the word Unset is added to the
    key value.
  3. Sometimes, the next Textfield is skipped and the cursor comes back to the
    first Textfield in the list. This time the key value is registered properly.

PierZen

@openstreetmap-trac
Copy link
Author

Author: robbieonsea
[Added to the original trac issue at 12.05am, Saturday, 21st April 2012]

I can't reproduce this behaviour with the latest 2.3 version.

Probably has been fixed since it was reported, but nothing obvious jumps out in the git logs that addresses this specific problem.

@openstreetmap-trac
Copy link
Author

Author: compdude
[Added to the original trac issue at 3.00am, Saturday, 26th October 2013]

I've never noticed this issue. Closing this bug.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@openstreetmap-trac openstreetmap-trac

Labels
Component: potlatch2 Priority: major Resolution: worksforme Type: defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@openstreetmap-trac