-
Notifications
You must be signed in to change notification settings - Fork 163
Visual Cell Merging
- Overview
- User Stories
- Functionality
- Test Scenarios
- Accessibility
- Assumptions and Limitations
- References
Team Name
Developer Name
Stefan Ivanov
- Peer Developer Name | Date:
- Stefan Ivanov | Date: 21 Sep 2020
- Product Owner Name | Date:
- Platform Architect Name | Date:
Version | User | Date | Notes |
---|---|---|---|
0.1 | Stefan Ivanov | Sep 21, 2020 | Spec and design initial creation |
Visually merging cells is a visual enhancement over the grid data, where a different style can be applied on consecutive cells within the same column with matching values. This reduces the cognitive perception of the grid and reduces the perceived visual complexity of the component, especially when large amounts of data are presented.
Define the high-level goals End-to-end user experience
Must-have before we can consider the feature a sprint candidate
...
Elaborate more on the multi-facetted use cases
Developer stories:
- Story 1: As a developer, I want to provide visually merged areas of cells by configuring a property on the grid, so that I can stress on some commonality in the data shown in the grid.
- Story 2: As a developer, I want to be able to customize the style of the area of the merged cells, so that I can make it more prominent or subtle.
- Story 3: As a developer, I expect that visual merging happens within the limits of a given grid column so that I can only fields with the same context of belonging are grouped together.
End-user stories:
- Story 1: As an end-user, I want to be able to easily identify areas in the data where consecutive values match, so that I can have a notion of items belonging together according to common data
Describe behavior, design, look and feel of the implemented feature. Always include visual mock-up
3.1. End-User Experience
** Integration scenarios or functionality with Multi-Column headers shows the bottom borders when there is a cell layout below, rather than a matching cell
** End-to-end user experience includes hiding the bottom borders between adjacent cells belonging to a visually merged collection of cells
** Prepared design files for styling e.g. interplay with features and light/dark variants
3.2. Developer Experience
3.3. Globalization/Localization
Describe any special localization requirements such as the number of localizable strings, regional formats
3.4. Keyboard Navigation
Keys | Description |
---|---|
3.5. API
Name | Description | Type | Default value | Valid values |
---|---|---|---|---|
Name | Description | Return type | Parameters |
---|---|---|---|
Name | Description | Cancelable | Parameters |
---|---|---|---|
Automation
- Scenario 1:
- scenario 2:
ARIA Support
RTL Support
Assumptions | Limitation Notes |
---|---|
Specify all referenced external sources