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

Typeahead: Invisible "ngb-live" element is not translatable and may be visible #4560

Open
nextgovitAS opened this issue Aug 31, 2023 · 0 comments · May be fixed by #4605
Open

Typeahead: Invisible "ngb-live" element is not translatable and may be visible #4560

nextgovitAS opened this issue Aug 31, 2023 · 0 comments · May be fixed by #4605

Comments

@nextgovitAS
Copy link

Description:

When using the typeahead component, a new element appears in the DOM indicating the number of results:

<div id="ngb-live" aria-live="polite" aria-atomic="true" class="visually-hidden">1 result available</div>

I have two problems with this:

  1. The printed message is in English, I need a way to translate it.
  2. My application is encapsulated in a shadow DOM but this new element is injected into the outside body. I have no control over the CSS outside the shadow DOM and therefore the element could be visible to the user. I need to be able to specify a container (within the shadow DOM) for this element.

Link to minimally-working StackBlitz that reproduces the issue:

https://stackblitz.com/edit/angular-te4ccq?file=src%2Findex.html

Versions

Angular: v16.1
ng-bootstrap: v15.1
Bootstrap: v5.2.3

jeremychoisy pushed a commit to jeremychoisy/ng-bootstrap that referenced this issue Nov 9, 2023
Use inline style instead of the bootstrap class for the live element
to support the usage of the component in the shadow DOM and localize the message itself.
Fixes ng-bootstrap#4560
jeremychoisy pushed a commit to jeremychoisy/ng-bootstrap that referenced this issue Nov 9, 2023
Use inline style instead of the bootstrap class for the live element
to support the usage of the component in the shadow DOM and localize the message itself.
Fixes ng-bootstrap#4560
jeremychoisy pushed a commit to jeremychoisy/ng-bootstrap that referenced this issue Nov 9, 2023
Use inline style instead of the bootstrap class for the live element
to support the usage of the component in the shadow DOM and localize the message itself.
Fixes ng-bootstrap#4560
jeremychoisy pushed a commit to jeremychoisy/ng-bootstrap that referenced this issue Nov 9, 2023
Use inline style instead of the bootstrap class for the live element
to support the usage of the component in the shadow DOM and localize the message itself.
Fixes ng-bootstrap#4560
jeremychoisy pushed a commit to jeremychoisy/ng-bootstrap that referenced this issue Nov 9, 2023
Use inline style instead of the bootstrap class for the live element
to support the usage of the component in the shadow DOM and localize the message itself.
Fixes ng-bootstrap#4560
jeremychoisy pushed a commit to jeremychoisy/ng-bootstrap that referenced this issue Nov 9, 2023
Use inline style instead of the bootstrap class for the live element
to support the usage of the component in the shadow DOM and localize the message itself.
Fixes ng-bootstrap#4560
jeremychoisy pushed a commit to jeremychoisy/ng-bootstrap that referenced this issue Nov 10, 2023
Use inline style instead of the bootstrap class for the live element
to support the usage of the component in the shadow DOM.
Fixes ng-bootstrap#4560
jeremychoisy pushed a commit to jeremychoisy/ng-bootstrap that referenced this issue Nov 10, 2023
Enable localization for the live element.
Fixes ng-bootstrap#4560
jeremychoisy pushed a commit to jeremychoisy/ng-bootstrap that referenced this issue Nov 10, 2023
Enable localization for the live element.
Fixes ng-bootstrap#4560
jeremychoisy pushed a commit to jeremychoisy/ng-bootstrap that referenced this issue Jan 22, 2024
Use inline style instead of the bootstrap class for the live element
to support the usage of the component in the shadow DOM.
Fixes ng-bootstrap#4560
jeremychoisy pushed a commit to jeremychoisy/ng-bootstrap that referenced this issue Jan 22, 2024
Enable localization for the live element.
Fixes ng-bootstrap#4560
jeremychoisy pushed a commit to jeremychoisy/ng-bootstrap that referenced this issue Jan 22, 2024
Use inline style instead of the bootstrap class for the live element
to support the usage of the component in the shadow DOM.
Fixes ng-bootstrap#4560
jeremychoisy pushed a commit to jeremychoisy/ng-bootstrap that referenced this issue Jan 22, 2024
Enable localization for the live element.
Fixes ng-bootstrap#4560
jeremychoisy pushed a commit to jeremychoisy/ng-bootstrap that referenced this issue Jan 22, 2024
Enable localization for the live element.
Fixes ng-bootstrap#4560
jeremychoisy pushed a commit to jeremychoisy/ng-bootstrap that referenced this issue Jan 22, 2024
Enable localization for the live element.
Fixes ng-bootstrap#4560
jeremychoisy pushed a commit to jeremychoisy/ng-bootstrap that referenced this issue Jan 22, 2024
Use inline style instead of the bootstrap class for the live element
to support the usage of the component in the shadow DOM.
Fixes ng-bootstrap#4560
jeremychoisy pushed a commit to jeremychoisy/ng-bootstrap that referenced this issue Jan 22, 2024
Enable localization for the live element.
Fixes ng-bootstrap#4560
jeremychoisy pushed a commit to jeremychoisy/ng-bootstrap that referenced this issue Jan 22, 2024
Enable the override of the container for the live element, through a DI token,
meaning that the Live service is not provided in root anymore and needs to be
provided when used in a component.
Fixes ng-bootstrap#4560
jeremychoisy pushed a commit to jeremychoisy/ng-bootstrap that referenced this issue Jan 22, 2024
Enable localization for the live element.
Fixes ng-bootstrap#4560
jeremychoisy pushed a commit to jeremychoisy/ng-bootstrap that referenced this issue Jan 23, 2024
Enable localization for the live element.
Fixes ng-bootstrap#4560
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants