Bug #1414
Enlarged Description Field Covers up Entry Buttons
Description
With the new update, it is possible to enlarge the description field until it covers the entry buttons. In that case they can't be used until the size of the field is reduced again.
We also tried to ask at Stackoverflow: https://stackoverflow.com/questions/66677704/positioning-adjacent-text-area-above-leaflet-map
Files
History
Updated by Alexander Watzinger about 1 year ago
Updated by - Category set to UI
- Status changed from New to Acknowledged
- Target version set to 6.0.0
Can confirm, thanks for reporting.
Updated by Alexander Watzinger about 1 year ago
- Status changed from Acknowledged to Assigned
- Assignee set to Christoph Hoffmann
- Found in version changed from 6.0.0 to 5.5.0
This bug seems to have exist before but wasn't that obvious because the buttons were positioned more to the left in former versions, see e.g. in 5.5.1: https://demo.openatlas.eu/source/insert
The culprit seems to be the absolute positioning in /static/css/style.css
.table-cell textarea {
z-index: 1;
position: absolute;
}
If I remember correctly we implemented this because otherwise an expanded textarea would vanish below the map at e.g. place insert. Assigning to Christoph because I'm out of my depth there.
Updated by Alexander Watzinger 12 months ago
I noticed also that in forms that don't have a big description field (e.g. value types, see: https://demo-dev.openatlas.eu/types/insert/21160) the fixed label size:
label[for="description"] {
height: 8em;
}
which seems to prevent the buttons from vanishing below larger description fields, is making a large gap in the form.
Again the culprit seems to be the absolute positioning which seems to make more problems than it solves.
Updated by Alexander Watzinger 10 months ago
- Target version changed from 6.1.0 to 6.2.0
Moving to next release to not block 6.1.0 release.
Updated by Alexander Watzinger 9 months ago
- Status changed from Assigned to Acknowledged
- Assignee deleted (
Christoph Hoffmann) - Target version changed from 6.2.0 to 6.3.0
Moving it to the next version because of lack of frontend developer capacities. Sorry for the inconvenience.
Updated by 
Updated by Christoph Hoffmann 7 months ago
- Status changed from Acknowledged to Closed
solution presented and accepted, to be released soon