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

CSS fix for Text/Textarea input fields language selector #560

Merged
merged 6 commits into from
Mar 15, 2020
Merged

CSS fix for Text/Textarea input fields language selector #560

merged 6 commits into from
Mar 15, 2020

Conversation

mjauvin
Copy link
Contributor

@mjauvin mjauvin commented Mar 11, 2020

  • add registerBundle() calls to allow compiling LESS files into CSS
  • make sure multi-lingual input form controls have padding-right of 44px

@mjauvin
Copy link
Contributor Author

mjauvin commented Mar 12, 2020

I noticed the language selector for textarea is problematic because of the scrollbar that appears dynamically once the content overflows:

before scrollbar appears (language selector can be obscured by text):
Screenshot from 2020-03-12 10-12-18

after scrollbar appears:
Screenshot from 2020-03-12 10-14-11

I propose we change the location of the language selector OUTSIDE of the field to cope for this, see screenshot below:

Screenshot from 2020-03-12 10-06-51

What do you guys think?

@LukeTowers
Copy link
Contributor

@mjauvin sounds good to me, just make sure it's on the same horizontal line as the field label

@bennothommo
Copy link
Contributor

@mjauvin You'll need to check the placement of the language selector when someone uses the commentAbove field option. If it stays there, then that's fine.

@mjauvin
Copy link
Contributor Author

mjauvin commented Mar 13, 2020

@bennothommo good point. Look at the following screenshot of a textarea with commentAbove:

Screenshot from 2020-03-12 22-20-15

Is that what you would expect?

@bennothommo
Copy link
Contributor

@mjauvin If possible, it should line up with the lowest element in the "label" portion of the field, so in this case, it should probably line up with the comment. But otherwise, it looks fine to me.

@mjauvin
Copy link
Contributor Author

mjauvin commented Mar 13, 2020

This is how it looks now with commentAbove:

Screenshot from 2020-03-13 01-24-52

@mjauvin mjauvin merged commit a6c6a66 into rainlab:master Mar 15, 2020
@mjauvin mjauvin changed the title Register asset bundle CSS fix for Text/Textarea input fields language selector Mar 15, 2020
@mjauvin mjauvin deleted the register-asset-bundle branch March 18, 2020 11:50
mjauvin added a commit that referenced this pull request Mar 20, 2020
* runs params value through htmlspecialchars() to escape html content

* add note about escaped content in translated messages

* use Html::clean() instead of e()

* Revert "add note about escaped content in translated messages"

* escape params when translating messages; introduce transRaw method for legacy usage

* Fix for #376 (#559)

Fix for #376

* Add support for transOrderBy (#516)

Add support for transOrderBy

* update version file for 1.6.8 release

* Disable safe mode checks for ML Static Pages.

Fixes rainlab/pages-plugin#434. Refs: rainlab/pages-plugin#174, rainlab/pages-plugin@6b6b061

* Clear RainLab.Pages caches when saving a static page

Fixes rainlab/pages-plugin#404

* Register asset bundle (#560)

* make sure multi-lingual input form controls have padding-right of 44px
* register asset bundle to process less files into css files
* reposition language selector above textarea box
* fix language selector position when commentAbove is defined

* Update version file for 1.6.9 release

* Fix error with casts fields default locale value (#556)

* only call setLocale() if locale has changed (#561)

* remove unused module

Co-authored-by: Siarhei Karavai <[email protected]>
Co-authored-by: Aurélien Roy <[email protected]>
Co-authored-by: Ben Thomson <[email protected]>
Co-authored-by: Luke Towers <[email protected]>
Co-authored-by: Trysystems <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants