Changes between Version 1 and Version 2 of Ticket #16580


Ignore:
Timestamp:
2018-08-07T20:20:22+02:00 (7 years ago)
Author:
Klumbumbus
Comment:

fixed in https://josm.openstreetmap.de/wiki/TaggingPresets?action=diff&version=145

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #16580

    • Property Resolution → fixed
    • Property Status new → closed

  • Ticket #16580 – Description

    v1 v2  
    1 TaggingPresets#Attributes says the following on the default values (explicitly set and implied):
     1The wiki says the following on the default values (explicitly set and implied):
    22
    3  default="default_value"::
    4   An explicitly declared default value for the item. This value is ''only'' applied through a preset when the object the preset is applied to has ''zero keys''.
    5   If a value for default is not given, different implied default values apply depending upon the type:
    6   * <check> (whether a checkbox is ticked on or off by default): implied default is "off"
    7   * <text>, <combo>, <multiselect>: implied default is ""
     3 default="default_value"
     4    An explicitly declared default value for the item. This value is only applied through a preset when the object the preset is applied to has zero keys. If a value for default is not given, different implied default values apply depending upon the type:
     5
     6        <check> (whether a checkbox is ticked on or off by default): implied default is "off"
     7        <text>, <combo>, <multiselect>: implied default is "" 
    88
    99However the actual JOSM behaviour seems to be to assume undefined / "" for <check> elements and not the default value for the "off" state ("no").