Skip to content
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

[UI] Form heading much shorter than needed #8980

Closed
jonasraoni opened this issue May 10, 2023 · 10 comments
Closed

[UI] Form heading much shorter than needed #8980

jonasraoni opened this issue May 10, 2023 · 10 comments
Assignees
Labels
Bug:1:Low A bug that does not have a severe consequence or affects a small number of users.
Milestone

Comments

@jonasraoni
Copy link
Contributor

Describe the bug
There are some headers enclosed with a .pkpFormGroup__heading, which limits the width in 30% (it should probably be used together with something else consuming the remaining 70%), which breaks texts in an unexpected way.

It's needed to inspect other usages across the codebase to define if it's a bug or a class misuse.

To Reproduce
Steps to reproduce the behavior:

  1. Go to Workflow Settings > Emails

What application are you using?
OJS 3.4rc2

Additional information
image

@jonasraoni jonasraoni changed the title Form heading much shorter than needed [UI] Form heading much shorter than needed May 10, 2023
@asmecher
Copy link
Member

@jonasraoni, is this a showstopper, or just annoying? Wondering whether to schedule for 3.4.0-0 or a subsequent build.

@jonasraoni
Copy link
Contributor Author

It's not important, I was just navigating on this interface to inspect a fatal error (#8975) and flagged the issues that I saw.

@asmecher asmecher added this to the 3.4.0-1 milestone May 10, 2023
@rahmanramsi
Copy link
Contributor

I think it supposed to be like this right?
image

@asmecher asmecher modified the milestones: 3.4.0-1, 3.4.0-2 Jun 16, 2023
@asmecher asmecher modified the milestones: 3.4.0-2, 3.4.0-3 Jul 24, 2023
@jardakotesovec jardakotesovec self-assigned this Aug 3, 2023
@jardakotesovec jardakotesovec added the Bug:1:Low A bug that does not have a severe consequence or affects a small number of users. label Aug 3, 2023
jardakotesovec added a commit to jardakotesovec/ui-library that referenced this issue Aug 3, 2023
jardakotesovec added a commit to jardakotesovec/ojs that referenced this issue Aug 3, 2023
jardakotesovec added a commit to jardakotesovec/omp that referenced this issue Aug 3, 2023
jardakotesovec added a commit to jardakotesovec/ops that referenced this issue Aug 3, 2023
@jardakotesovec
Copy link
Contributor

jardakotesovec commented Aug 3, 2023

This was happening in chrome based browsers as it does not support the css property float: inline-start; yet. It worked fine in firefox/safari - thats probably why it was overlooked.

To address it I added fallback float properties that are widely supported. In similar situation in future its better to move the layout from float to flex as flex has good support for RTL languages out of the box. But to keep the changes simple for now I sticked with float.

PRs:
ui-library: pkp/ui-library#279
ojs: pkp/ojs#3994
omp: pkp/omp#1435
ops: pkp/ops#550

@jardakotesovec
Copy link
Contributor

@asmecher @Vitaliy-1 Not sure whether its too late for it, but maybe this could be considered for 3.4.0-2. It affects quite a lot of screens - its just layout.. but still quite significant. Including multilingual forms that looks broken. It affects all chrome based browsers, which is also quite significant. I did test the changes carefully...

@Vitaliy-1
Copy link
Collaborator

Vitaliy-1 commented Aug 4, 2023

Looks good! Just a comment regarding commenting and it's ready to go to the stable and main.

In similar situation in future its better to move the layout from float to flex as flex has good support for RTL languages out of the box

At the time of development, flex was too young standard to adopt without consequences (in terms of browser support). We can decide to heighten the requirements as it's quite mature enough now. Edit sorry, was thinking about grid layout.

jardakotesovec added a commit to jardakotesovec/ui-library that referenced this issue Aug 4, 2023
@jardakotesovec
Copy link
Contributor

@Vitaliy-1 Good feedback, thanks. I end up removing both comment and the original inline-start as you pointed out it will take long time before that has good browser support. And reason for change is in commit message, which also reference this issues for more details, so I think that should be sufficient.

@asmecher
Copy link
Member

asmecher commented Aug 4, 2023

Thanks, and agreed, this is a good candidate for 3.4.0. @Vitaliy-1 and @jardakotesovec, I'll leave this to you two to merge and port when you're both ready.

@asmecher asmecher modified the milestones: 3.4.0-3, 3.4.0-2 Aug 4, 2023
jardakotesovec added a commit to pkp/ui-library that referenced this issue Aug 4, 2023
pkp/pkp-lib#8980 Add fallbacks for float inline-start due limited bro…
jardakotesovec added a commit to pkp/ui-library that referenced this issue Aug 4, 2023
@jardakotesovec
Copy link
Contributor

@asmecher @Vitaliy-1 Its now merged to 3.4.0 and cherry-picked for main.

@asmecher
Copy link
Member

asmecher commented Aug 4, 2023

Excellent, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug:1:Low A bug that does not have a severe consequence or affects a small number of users.
Projects
None yet
Development

No branches or pull requests

5 participants