Closed
Bug 889622
Opened 12 years ago
Closed 12 years ago
Calendar pop-up is underneath the map
Categories
(Mozilla Reps Graveyard :: reps.mozilla.org, task)
Mozilla Reps Graveyard
reps.mozilla.org
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 856994
People
(Reporter: hoosteeno, Unassigned)
Details
Attachments
(1 file)
|
785.19 KB,
image/png
|
Details |
When the calendar pop up on /events is close to the bottom of the screen, it appears _above_ the form field rather than _below_. And when it does that, it is z-indexed lower than the map itself.
Screenshot:
http://awesomescreenshot.com/0981go5v78
| Reporter | ||
Updated•12 years ago
|
Version: 401 → unspecified
| Reporter | ||
Comment 1•12 years ago
|
||
Comment 2•12 years ago
|
||
The datepicker div is getting an inline style of z-index: 1, which seems to be coming from this line in jquery-ui:
https://github.com/mozilla/remo/blob/master/media/js/libs/jquery-ui-1.10.0.custom.js#L1053
If I read that right, it gets the z-index value of the associated form field and adds 1. The field in this case has no explicit z-index (just the default z-index:auto), hence, the script inserts an explicit z-index: 1 because it treats auto as 0.
Then in app.less, this line:
https://github.com/mozilla/remo/blob/master/media/css/remo/app.less#L1399
Reads:
.ui-datepicker {
z-index: 200px;
}
where 200px isn't a valid value for z-index so it's being ignored. I'm sure that's just a typo and was meant to be z-index: 200, but even then I'm not sure it would take effect since the inline z-index: 1; might still override it in the cascade order (I haven't actually tried).
Possible fixes:
1. Fix the z-index: 200px; in app.less and see if that overrides the inline style.
2. If that doesn't work, give the date field a z-index that the script will read and +1 so we get a higher inline value on the div.
| Reporter | ||
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → DUPLICATE
Updated•5 years ago
|
Product: Mozilla Reps → Mozilla Reps Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•