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

Error/Validation messages don't appear in red in bootstrap-4. Using CSS did not resolve issue. #315

Open
4 tasks
jpuvogel13 opened this issue Mar 4, 2022 · 0 comments

Comments

@jpuvogel13
Copy link

Describe the bug
The error/validation messages only appear in black when using bootstrap-4 framework. Also, they don't appear after being touched, like they do in Material. I tried to override CSS properties, but unable to do so without turning description text red as well.
which template:

  • MaterialDesignFrameworkModule — Material Design
  • Bootstrap3FrameworkModule — Bootstrap 3
  • [X ] Bootstrap4FrameworkModule — Bootstrap 4
  • NoFrameworkModule — plain HTML
  • Other (please specify below)

A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

  1. Use bootstrap-4 framework, have required field in form.
  2. Touch required field, no message appears. Type a few characters then erase all, error message appears but in black only.
  3. ovverride Css class like so: ::ng-deep form-group schema-form-text has-error{
    p{
    color: red;
    }
    this now turns error messages red, however now description of input field is also red too.

Expected behavior
I expect error messages to appear in red font, and once the field is touched.

Screenshots
image

Desktop (please complete the following information):

  • OS: [e.g. iOS]
  • Windows
  • Browser [e.g. chrome, safari]
  • Chrome
E-Fir added a commit to logiceditor-com/ajsf that referenced this issue Nov 8, 2022
updateValue: mark as dirty before setting the value in order to run validation
Fixes hamzahamidi#315
E-Fir added a commit to logiceditor-com/ajsf that referenced this issue Nov 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant