-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Label formatting: move global styles away from label template #615
Comments
@mickley this is a short description of something you've commented regarding our label styles |
@arbolitoloco I think your CSS knowledge is probably better than mine, but I found that fieldblocks were showing up on the same line until I added |
GregoryPost
referenced
this issue
in BioKIC/Symbiota
Oct 10, 2022
Various BioKIC:Symbiota-light developments
egbot
referenced
this issue
in BioKIC/Symbiota
Jun 27, 2024
Merge various Symbiota-light developments into Lichen code repositories
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Historically there are some design choices made directly in collections/reports/labeldynamic.php that affect the printed labels and are controlled by different parts of the label format editor.
Specifically talking about the styles used for :
.row
(uses flexbox, which might not be the ideal way to position things, since it's responsive and we might want to be more strict about layouts);.label
(uses width percentage based on proportion selected by number of columns in label format editor, which might prevent users from easily adjusting very specific label fixed sizes);.label-header
and.label-footer
(use clear methods that might result in weird overlapping depending on other choices)Ideally we would be able to move these choices from the page itself to either global, custom, or label-specific styles, so that users can have easier control over design. To do that, the label editor and related classes, as well as default formats and styles will have to be adjusted as to not create problems for existing portals.
The text was updated successfully, but these errors were encountered: