GPX-tracks: nodes not deleted when line is removed

[jumat@…]

What steps will reproduce the problem?

1. import a GPX-file
2. cut the track into smaller pieces, e.g. with 10 nodes each.
3. click on the GPX-line (not on the node), so that the line is highlighted
4. press DEL

What is the expected result?

Deleting the line should delete also each node of the line

What happens instead?

Each node of the line is still displayed.
Another point is, that deleting nodes of a GPX file takes lots of time: I have tried to delete GPX-nodes with approx. 50/100/200 nodes and the longer the track is (the more nodes are affected) the longer deleting takes. For 200 nodes I'am waiting approx. 1 minute and in this timespan JOSM is blocked.

Please provide any additional information below. Attach a screenshot if possible.

URL:https://josm.openstreetmap.de/svn/trunk
Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2018-07-29 00:41:59 +0200 (Sun, 29 Jul 2018)
Build-Date:2018-07-29 01:32:17
Revision:14066
Relative:URL: ^/trunk

Identification: JOSM/1.5 (14066 de) Mac OS X 10.13.6
OS Build number: Mac OS X 10.13.6 (17G65)
Memory Usage: 686 MB / 1820 MB (285 MB allocated, but free)
Java version: 1.8.0_171-b11, Oracle Corporation, Java HotSpot(TM) 64-Bit Server VM
Screen: Display 685389249 1920x1200
Maximum Screen Size: 1920x1200
VM arguments: [-Djava.library.path=/private/var/folders/fc/bv6j_0k50dq0vwz0_0nn3dq00000gn/T/AppTranslocation/455F7F83-D2DC-462F-9D9B-205835537DF4/d/JOSM.app/Contents/MacOS, -DLibraryDirectory=${HOME}/Library, -DDocumentsDirectory=${HOME}/Documents, -DApplicationSupportDirectory=${HOME}/Library/Application Support, -DCachesDirectory=${HOME}/Library/Caches, -DSandboxEnabled=false, -Dapple.laf.useScreenMenuBar=true, -Dcom.apple.macos.use-file-dialog-packages=true, -Dcom.apple.macos.useScreenMenuBar=true, -Dcom.apple.mrj.application.apple.menu.about.name=JOSM, -Dcom.apple.smallTabs=true]
Dataset consistency test: No problems found

Plugins:
+ austriaaddresshelper (1525848529)
+ buildings_tools (34212)
+ continuosDownload (1530471163)
+ contourmerge (v0.1.0)
+ editgpx (34206)
+ utilsplugin2 (34389)

Map paint styles:
+ https://pasharm.github.io/New_basic_style_for_JOSM/New_basic_style.mapcss

Validator rules:
+ resource://data/validator/power.mapcss

Last errors/warnings:
- W: Unable to convert property color to type class java.awt.Color: found # of type class java.lang.String!
- W: Unable to convert property color to type class java.awt.Color: found # of type class java.lang.String!
- W: Unable to convert property color to type class java.awt.Color: found # of type class java.lang.String!
- W: Unable to convert property color to type class java.awt.Color: found # of type class java.lang.String!
- W: Unable to convert property color to type class java.awt.Color: found # of type class java.lang.String!
- W: Unable to convert property color to type class java.awt.Color: found # of type class java.lang.String!
- W: Unable to convert property color to type class java.awt.Color: found # of type class java.lang.String!
- W: Unable to convert property color to type class java.awt.Color: found # of type class java.lang.String!
- W: Unable to convert property color to type class java.awt.Color: found # of type class java.lang.String!
- W: Unable to convert property color to type class java.awt.Color: found # of type class java.lang.String!

[Don-vip]

Closed as duplicate of #16572.
Side effect of nodes being tagged. With #16572 fixed you now have the option to restore old behaviour (untagged nodes)

[Bjoeni]

Shouldn't it be anyways up to the user if he wants to delete tagged nodes in a line or not?
Not just for converted GPX tracks but also when deleting existing OSM lines, users might not be aware of tagged nodes in the line and miss them.

[Klumbumbus]

It is the most sensible and most expected solution to delete untagged way nodes and keep tagged way nodes when deleting a way.
If you want to delete way nodes too select them before deleting e.g. via wiki:/Help/Action/SelectWayNodes or wiki:/Help/Action/Search

[Bjoeni]

I'd agree with that, if JOSM didn't decide about "uninteresting" nodes on its own (the getUninterestingKeys-Method in data.osm.AbstractPrimitive). Because the first time I used JOSM I actually assumed that all nodes would always be deleted (I just tried it with fixme-Tags and stuff that was deemed uninteresting)