id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
19805	MapCSS meaning of 'none'	frodrigo	team	"combinations.mapcss now provide this rule

{{{
789	*[fixme][count(split("" "", tag(""fixme""))) == 1][tag(tag(""fixme"")) != ""none""],
790	*[FIXME][count(split("" "", tag(""FIXME""))) == 1][tag(tag(""FIXME"")) != ""none""] {
791	  throwWarning: tr(""{0} together with {1}. Is the fixme fixed?"", ""{0.tag}"", ""{0.value}"");
792	  group: tr(""suspicious tag combination"");
793	  assertMatch: ""way name=\""Florist Gump\"" fixme=name"";
794	  assertMatch: ""way name=\""Florist Gump\"" FIXME=name"";
795	  assertNoMatch: ""way fixme=name"";
796	  assertNoMatch: ""way name=\""Florist Gump\"""";
797	  assertNoMatch: ""way name=\""Florist Gump\"" fixme=\""the name might have changed\"""";
798	}
}}}

I concerned about this part
{{{
[tag(tag(""fixme"")) != ""none""]
}}}

It checks if there is no key like the value of fixme key. But comparing to the ""none"" string.

It asserted with
{{{
795	  assertNoMatch: ""way fixme=name"";
}}}

It strange to me to check ""none"" string as not existing tags.

This assert fails on Osmose-QA MapsCSS implementation."	defect	closed	normal	20.09	Core validator		fixed	mapcss, osmose	taylor.smock