Opened 15 years ago
Closed 14 years ago
#5950 closed defect (fixed)
z-index does not affect casing
| Reported by: | anonymous | Owned by: | bastiK |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Core | Version: | latest |
| Keywords: | mapcss, mappaint | Cc: |
Description
this rule will only overlay the inner line, not the outer casings:
way[bridge=yes]
{
casing-width:+3;
casing-color:white;
z-index:4;
}
Attachments (0)
Change History (5)
comment:1 by , 15 years ago
| Owner: | changed from to |
|---|
follow-up: 3 comment:2 by , 15 years ago
follow-up: 4 comment:3 by , 15 years ago
Would it be feasible to use the z-index of the line -1 instead of a constant?
(I also observed that the MapCSS 0.2 proposal suggests to change the casing-width from total width to "extra width on each side". I think the casing-width:+1; is better, as it is backwards compatible.)
comment:4 by , 15 years ago
Replying to Vidar Gundersen:
Would it be feasible to use the z-index of the line -1 instead of a constant?
I don't want any line be below any casing. If secondary and residential road meet at a junction (and they have z-index difference of 2 or more) this would be the case. I agree that it should be "z-index of line - n". What is the disadvantage of n=100? If there is any, n=20 would be fine, I guess.
(I also observed that the MapCSS 0.2 proposal suggests to change the casing-width from total width to "extra width on each side". I think the casing-width:+1; is better, as it is backwards compatible.)
+1, not so much because of backwards compatibility, but because it offers 2 options:
- either relative:
casing-width: +2; - or absolute:
casing-width: 13;



At the moment, casings have a constant z-index (-100). What do you suggest? Btw. casing is nothing more than a second line below, so it is really just a shortcut.