Text input: v11 audit
See original GitHub issueAudit
A designer and developer will pair on this audit, some tasks may be discipline focused. Follow the checklist below for the features and items to review. If there are no issues with the item then check the item as complete. If any problems or bugs come up when auditing add a comment to this issue with the problem and how to correct it (if you know how). Bugs do not need to be fixed while auditing.
Resources
Variants
- Text input
- Password input
- Text area
Checklist
Visual (in React code) Design and dev check
- Component is using the correct design tokens (color and type), see design spec and scss code.
- Component is rendering correctly across themes and layers, see design spec and storybook.
- White theme
- Gray 10 theme
- Gray 90 theme
- Gray 100 theme
- Component is rendering correctly across browsers (check themes across browsers as well), see storybook.
- Firefox
- Safari
- Chrome
- Component sizes are rendering and named correctly (if applicable)
Website (v11) Design checks
- Style tab has correct design tokens listed
- Style and usage tabs are using the correct size props names (if applicable)
- Usage tab is up-to-date for with any v11 behavioral changes (if any)
- Live Demo has applied v11 changes
- Themes are rendering correctly
- Size props are named correctly
- No
light
props included
Design Kits (Sketch only) Design checks
- Correct design tokens (type and color) are used
- Component using the correct size prop names
- Any additional v11 behaviors have been added
Storybook Dev checks
- Confirm that prop table is populating
- Take note of missing examples/stories (if any)
React package Dev checks
- Go to https://codesandbox.io/s/github/carbon-design-system/carbon/tree/main/packages/react/examples/codesandbox and confirm that you can use the component as expected from
@carbon/react
Accessibility Dev checks
- Confirm that there are no violations in Accessibility checker
- Confirm that component works as expected with VoiceOver
Migration docs Design and dev check
- Any breaking changes to this component are present in the v11 migration guide.
- Design
- Develop
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Enterprise 11 Audit API - Automation Anywhere Documentation
Requests audit data for a given input combination of date filter, sorting mechanism, and pagination.
Read more >Configuring Imperva SecureSphere V11.0 to V13 to ... - IBM
To send database audit records from Imperva SecureSphere V11.0 to V13 IBM QRadar, ... In the Action Set text box, type a name...
Read more >Intergy v11.0 - Greenway Health
Auditing. • More. • Practice. Management. • Patient Portal ... clients' input. ... A new goal will be created with the text from...
Read more >Tech Tip: IDEA 11 Labs: WORD FIND and TEXT ANALYSIS
This plugin creates a summary of all the words from a selected text field within an IDEA database. The user is given the...
Read more >List of Changes for Laserfiche 11 - Knowledge Base
Laserfiche Audit Trail 11 introduces a new audit reporting ... (190848); Resolved an issue that could cause text box annotations to be ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Live Demo
Modifiers side needs to update:
light
propPassword input variant has a bug and missing all the modifiers
Design kit