Opened 5 years ago
Last modified 4 years ago
#19468 new defect
Delete Tag button tool tip block click event
Reported by: | Owned by: | team | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Core | Version: | |
Keywords: | template_report | Cc: |
Description
What steps will reproduce the problem?
- Open JOSM, select an element, open the "Tags" pane.
- Hover mouse over the "Delete" button in the "Tags" pane.
- Observe that the tool tip appears directly between the mouse and the button.
- Try to click the button.
What is the expected result?
I expect the clicking the mouse over the Delete button to result in the button being clicked.
What happens instead?
The tool tip text blocks the click.
Please provide any additional information below. Attach a screenshot if possible.
I could reproduce the issue on the "Edit" Tag button also.
The "Add" Tag button work as expected.
Relative:URL: ^/trunk Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b Last:Changed Date: 2020-06-02 08:27:29 +0200 (Tue, 02 Jun 2020) Revision:16538 Build-Date:2020-06-02 11:11:35 URL:https://josm.openstreetmap.de/svn/trunk Identification: JOSM/1.5 (16538 en) Windows 10 64-Bit OS Build number: Windows 10 Home 1909 (18363) Memory Usage: 2048 MB / 2048 MB (236 MB allocated, but free) Java version: 13.0.2+8, AdoptOpenJDK, OpenJDK 64-Bit Server VM Look and Feel: com.sun.java.swing.plaf.windows.WindowsLookAndFeel Screen: \Display0 3840x2160 Maximum Screen Size: 3840x2160 Dataset consistency test: No problems found Plugins: + Mapillary (1.5.23) + apache-commons (35362) + apache-http (35092) + ejml (35313) + geotools (35169) + javafx-windows (35458) + jaxb (35092) + jna (35092) + jts (35122) + measurement (35405) + opendata (35405) + pbf (35446) + poly (35248) + todo (30306) + touchscreenhelper (35248) + undelete (35474) + utilsplugin2 (35476) Map paint styles: - https://josm.openstreetmap.de/josmfile?page=Styles/Coloured_Streets&zip=1 - %UserProfile%\Desktop\Render a Field as Text.mapcss - https://josm.openstreetmap.de/josmfile?page=Styles/Maxspeed&zip=1 Last errors/warnings: - W: java.net.SocketTimeoutException: Connect timed out - E: java.net.SocketTimeoutException: Connect timed out - W: org.openstreetmap.josm.io.OsmTransferException: Could not connect to the OSM server. Please check your internet connection.. Cause: java.net.SocketTimeoutException: Connect timed out - W: java.net.SocketTimeoutException: Read timed out. Cause: java.net.SocketTimeoutException: Read timed out - E: java.lang.InterruptedException - E: java.lang.InterruptedException - W: java.net.SocketTimeoutException: Read timed out. Cause: java.net.SocketTimeoutException: Read timed out - W: Could not read from URL https://a.mapillary.com/v3/sequences?client_id=UTZhSnNFdGpxSEFFREUwb01GYzlXZzpjNGViMzQxMTIzMjY0MjZm&bbox=-70.2139986%2C43.7273031%2C-70.2109972%2C43.7287044!: java.net.SocketTimeoutException: Read timed out. Cause: java.net.SocketTimeoutException: Read timed out - W: java.net.SocketTimeoutException: Read timed out. Cause: java.net.SocketTimeoutException: Read timed out - W: Could not read from URL https://a.mapillary.com/v3/sequences?client_id=UTZhSnNFdGpxSEFFREUwb01GYzlXZzpjNGViMzQxMTIzMjY0MjZm&bbox=-70.2134702%2C43.7270085%2C-70.2104688%2C43.7284098!: java.net.SocketTimeoutException: Read timed out. Cause: java.net.SocketTimeoutException: Read timed out
Attachments (1)
Change History (3)
by , 5 years ago
Attachment: | ButtonBlock.png added |
---|
comment:2 by , 4 years ago
Strange… We're setting a normal tooltip (via Action#SHORT_DESCRIPTION
), there's no magic.
I can reproduce this issue on Linux. Clicking on the tooltip makes the tooltip disappear, only a second click activates the button.
Revision:16786 Is-Local-Build:true Build-Date:2020-07-17 23:23:44 Identification: JOSM/1.5 (16786 SVN en) Linux Arch Linux Memory Usage: 102 MB / 3969 MB (21 MB allocated, but free) Java version: 14+36, AdoptOpenJDK, Eclipse OpenJ9 VM Look and Feel: javax.swing.plaf.metal.MetalLookAndFeel Screen: :0.0 3840x2160 (scaling 1.0x1.0) Maximum Screen Size: 3840x2160 Best cursor sizes: 16x16 -> 16x16, 32x32 -> 32x32 Dataset consistency test: No problems found
A picture of the button being clocked