javascript/ionic-framework
1
0
Fork 0
mirror of https://github.com/ionic-team/ionic-framework.git synced 2025-11-03 03:13:42 +08:00
Code Issues Packages Projects Releases Wiki Activity
Files
ionic-framework/packages/angular
History
Shane c339bc3682 fix(input): improve error text accessibility (#30635) 
Issue number: resolves internal

---------

<!-- Please do not submit updates to dependencies unless it fixes an
issue. -->

<!-- Please try to limit your pull request to one type (bugfix, feature,
etc). Submit multiple pull requests if needed. -->

## What is the current behavior?
<!-- Please describe the current behavior that you are modifying. -->

Currently, when an error text is shown, it may not announce itself to
voice assistants. This is because the way error text currently works is
by always existing in the DOM, but being hidden when there is no error.
When the error state changes, the error text is shown, but as far as the
voice assistant can tell it's always been there and nothing has changed.

## What is the new behavior?
<!-- Please describe the behavior or changes that are being added by
this PR. -->

With these changes, both input and textarea have been updated so they'll
properly announce error text when it shows up. We had to do this with a
mutation observer and state because it's important in some frameworks,
like Angular, that state changes to cause a re-render. This, combined
with some minor aria changes, makes it so that when a field is declared
invalid, it immediately announces the invalid state instead of waiting
for the user to go back to the invalid field.

## Does this introduce a breaking change?

- [ ] Yes
- [X] No

<!--
  If this introduces a breaking change:
1. Describe the impact and migration path for existing applications
below.
  2. Update the BREAKING.md file with the breaking change.
3. Add "BREAKING CHANGE: [...]" to the commit description when merging.
See
https://github.com/ionic-team/ionic-framework/blob/main/docs/CONTRIBUTING.md#footer
for more information.
-->


## Other information

<!-- Any other information that is important to this PR such as
screenshots of how the component looks before and after the change. -->

Current dev build:
```
8.7.4-dev.11756220757.185b8cbf
```

## Screens

[Textarea](https://ionic-framework-git-ionic-49-ionic1.vercel.app/src/components/textarea/test/validation)

[Input](https://ionic-framework-git-ionic-49-ionic1.vercel.app/src/components/input/test/validation)

---------

Co-authored-by: Brandy Smith <brandyscarney@users.noreply.github.com>
2025-09-04 15:11:59 +00:00
..
common
feat(modal): add IonModalToken for injecting modal elements in Angular components (#30474)
2025-07-30 16:43:02 -04:00
scripts
fix(overlays,picker): remove invalid aria-hidden attribute (#30563)
2025-09-03 22:54:11 +00:00
src
feat(modal): add IonModalToken for injecting modal elements in Angular components (#30474)
2025-07-30 16:43:02 -04:00
standalone
feat(modal): add IonModalToken for injecting modal elements in Angular components (#30474)
2025-07-30 16:43:02 -04:00
test
fix(input): improve error text accessibility (#30635)
2025-09-04 15:11:59 +00:00
.eslintignore
refactor(angular): move to packages directory (#27719)
2023-07-05 17:52:35 +00:00
.eslintrc.json
refactor(angular): move to packages directory (#27719)
2023-07-05 17:52:35 +00:00
.prettierignore
fix(angular): standalone form components do not error when multiple are used (#28423)
2023-10-27 19:08:54 +00:00
CHANGELOG.md
v8.7.3
2025-08-20 18:36:46 +00:00
ng-package.json
refactor(angular): move to packages directory (#27719)
2023-07-05 17:52:35 +00:00
package-lock.json
chore(): update package lock files
2025-08-20 18:37:37 +00:00
package.json
fix(overlays,picker): remove invalid aria-hidden attribute (#30563)
2025-09-03 22:54:11 +00:00
README.md
fix(angular): update schematics to support Angular's latest build system (#30525)
2025-07-02 15:23:43 +00:00
tsconfig.json
chore(angular): type checking for standalone directory (#28531)
2023-11-15 18:58:27 +00:00
tsconfig.schematics.json
refactor(angular): move to packages directory (#27719)
2023-07-05 17:52:35 +00:00

README.md

@ionic/angular

Ionic Angular specific building blocks on top of @ionic/core components.

Related

License

Testing Local Ionic Framework with ng add

This guide shows you how to test the local Ionic Framework build with a new Angular application using ng add. This is useful for development and testing changes before publishing.

Prerequisites

  • Node.js and npm installed
  • Angular CLI installed globally (npm install -g @angular/cli)

Build Local Ionic Framework

  1. Clone the repository (if not already done):

    git clone https://github.com/ionic-team/ionic-framework.git
cd ionic-framework

  2. Pull the latest from main

    git pull origin main

  3. Install dependencies and build the core package:

    cd core
npm install
npm run build

  4. Install dependencies, sync the core build and build the Angular package:

    cd ../packages/angular
npm install
npm run sync
npm run build

  5. Create a tarball:

    cd dist
npm pack

  6. Copy the tarball to Downloads:

    cp ionic-angular-*.tgz ~/Downloads/ionic-angular.tgz

Test with New Angular App

  1. Create a new Angular app:

    # Change to whichever directory you want the app in
cd ~/Documents/
ng new my-app --style=css --ssr=false --zoneless=false
cd my-app

  2. Install the local @ionic/angular package:

    npm install ~/Downloads/ionic-angular.tgz

  3. Run ng add:

    ng add @ionic/angular --skip-confirmation

  4. Serve the app:

    ng serve

The local Ionic Framework build is now active in the Angular app. Changes to the Ionic source code require rebuilding the packages and reinstalling the tarball to see updates.

Project Structure

common

This is where logic that is shared between lazy loaded and standalone components live. For example, the lazy loaded IonPopover and standalone IonPopover components extend from a base IonPopover implementation that exists in this directory.

Note: This directory exposes internal APIs and is only accessed in the standalone and src submodules. Ionic developers should never import directly from @ionic/angular/common. Instead, they should import from @ionic/angular or @ionic/angular/standalone.

standalone

This is where the standalone component implementations live. It was added as a separate entry point to avoid any lazy loaded logic from accidentally being pulled in to the final build. Having a separate directory allows the lazy loaded implementation to remain accessible from @ionic/angular for backwards compatibility.

Ionic developers can access this by importing from @ionic/angular/standalone.

src

This is where the lazy loaded component implementations live.

Ionic developers can access this by importing from @ionic/angular.