microsoft / microsoft/fluentui

Component: Toolbar

Open
#26,717 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Component: Toolbar Fluent UI WC (v3) Resolution: Soft Close Type: Epic web-components
Dominant language
TypeScript
Stars
20.3k
Forks
2.9k
Avg merge
2d 9h
Merged PRs (30d)
46

Description

Component Name

Component Description

Design Spec

Link to Design Spec in Figma

Engineering Spec

Inputs
  • [List all inputs into the component]
  • [e.g. @attr public paused: boolean | false]
Outputs
  • [List all outputs from the component]
Events
  • [List all inputs into the component]
Slots
  • [List all named and unnamed slots for the component]
  • [e.g. Indeterminate: The slot for a custom indeterminate indicator]
CSS Variables
  • [Any component-specific CSS variables that allow the user to change the appearance of the component]

Accessibility

Preparation

Implementation

  • Initial conformance and unit tests (validate basic functionality)
  • Initial documentation
  • Uses design tokens for styling
  • Renders correctly in High Contrast mode

Validation

  • Add tests
    • Unit and conformance tests
    • Bundle size fixtures
    • Performance test scenario
    • Accessibility behavior tests
    • Create an issue and run manual accessibility tests: [link to issue]
  • Validate with partners
  • Finalize documentation
    • Review and add any missing storybook stories
    • Finalize migration guide
    • In package.json: Remove the alpha/beta tag from the version number in package.json
    • In package.json: Change beachball's disallowedChangeTypes to "major", "prerelease"

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the component specification and implementation guide linked in the issue, then compare the FAST Component documentation, Fluent UI React V9 specs, and Storybook. The design, engineering, accessibility, implementation, validation, and documentation sections are still unfilled; completion would require resolving those requirements and adding the listed tests and documentation.

Written by the indexing model from the issue text.

Assessment

Tech stack
react, typescript
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.