Changes between Version 197 and Version 198 of Help/Styles/MapCSSImplementation


Ignore:
Timestamp:
2021-11-07T12:40:06+01:00 (4 years ago)
Author:
skyper
Comment:

use CamelCase for anchors; use consistent link syntax

Legend:

Unmodified
Added
Removed
Modified

  • Help/Styles/MapCSSImplementation

    v197 v198  
    206206* The functions ''prop()'' and ''is_prop_set()'' are only supported on the right side of the > sign.
    207207* The functions ''parent_tag'' and ''parent_tags'' (see below) can be used to access tags from the parent(s).
    208 * For compatibility with the MapCSS 0.2 standard, `relation[type=route][route=foot] way {/*...*/}`, without the greater-than-sign `>` is supported, too. However, no [[#Linkselector|Link selector]] may be specified in this case.
     208* For compatibility with the MapCSS 0.2 standard, `relation[type=route][route=foot] way {/*...*/}`, without the greater-than-sign `>` is supported, too. However, no [#LinkSelector Link selector] may be specified in this case.
    209209
    210210=== Parent selector ===
    … …  
    583583}}}
    584584
    585 === Link selector === #Linkselector
     585=== Link selector ===#LinkSelector
    586586In a child selector, you can formulate conditions on the link between a parent and a child object.
    587587
    … …  
    656656The precise definition of scale ranges for each zoom level may change in the future. By rule of thumb you can expect to be approximately at zoom level ''n'' when imagery displays slippymap tiles of level ''n''.
    657657
    658 === Pseudo Classes === #PseudoClasses
     658=== Pseudo Classes ===#PseudoClasses
    659659See [/doc/org/openstreetmap/josm/gui/mappaint/mapcss/ConditionFactory.PseudoClasses.html Javadoc] for the up-to-date list of pseudo classes supported by JOSM's MapCSS implementation.
    660660