fundamental-styles
fundamental-styles copied to clipboard
Horizon/Quartz Smoke testing
- [ ] Test the components in all themes before the Horizon release.
- [ ] Distinguish the release blockers
- [ ] Bug fixes
Browsers for testing:
- [ ] Firefox - @g-cheishvili
- [ ] Edge - @platon-rov
- [ ] Chrome - @InnaAtanasova
- [ ] Safari - @N1XUS
Themes for testing:
- [ ] Quartz Light or Dark
- [ ] Horizon Morning
- [ ] Horizon Evening
- [ ] HCB for Horizon or HCW for Horizon
RTL and LTR testing too
Components for testing:
- [ ] Avatar
- [ ] Icons
- [ ] Busy Indicator
- [ ] Button Components - Badge on Button
- [ ] Button Components - Button
- [ ] Button Components - Button Shortcuts
- [ ] Button Components - Menu Button
- [ ] Button Components - Segmented Button
- [ ] Button Components - Toggle Button
- [ ] Calendar Components - Date Picker
- [ ] Checkbox
- [ ] Dialog and Popover Components - Dialog
- [ ] Dialog and Popover Components - Popover
- [ ] Dialog and Popover Components - Message Box
- [ ] Toolbar and Bar
- [ ] Input Components - Combobox
- [ ] Input Components - Input Field
- [ ] Step Input
- [ ] Input Group
- [ ] Input Components - Multi Input and Multi Combo
- [ ] Message Strip
- [ ] Page and Layout
- [ ] Dynamic Page
- [ ] Dynamic Side Content
- [ ] Flexible Column Layout
- [ ] Message Page
- [ ] Page
- [ ] Radio Button
- [ ] Switch
- [ ] Tab Bar
- [ ] Text Components
- [ ] Cards and Tiles
- [ ] Shellbar
- [ ] Input Components - Dropdown
- [ ] List View
- [ ] List
- [ ] GridList
- [ ] ObjectList
- [ ] Table
Carryover from #3327
- [x] #3477
- [x] #3465
- [x] #3474
- [x] Tree, Fiori/Horizon, HC. Focus on the expanders look quite different from all other elements. Also state active is missing. However i didn't find how it should look like, probably we should ask designers about it. EDIT temp solution here before speaking w/ designers: https://github.com/SAP/fundamental-styles/pull/3511
Create a separate issue for future testing and integration with ngx
- [x] Button: Icon & text example is broken
FIXED
- [x] Horizon carousel: text is not filly visible https://github.com/SAP/fundamental-styles/pull/3513
- [x] Avatar - the focus is not per specs. - https://github.com/SAP/fundamental-styles/pull/3505
Fund-styles:
Specs:
Fund-styles Avatar Group:

bring the question in the Horizon thread
- [x] IconTabBar focus issues (Horizon) https://github.com/SAP/fundamental-styles/pull/3517
-
[x] Menu focus issues (Horizon) - https://github.com/SAP/fundamental-styles/pull/3510
-
[x] Disabled Menu element gets a focus: - https://github.com/SAP/fundamental-styles/pull/3510
- [x] Micro Process Flow (Horizon) - focus issue: @N1XUS https://github.com/SAP/fundamental-styles/pull/3507
- [x] Progress Indicator - issue when the bar is at 0% (Horizon) - https://github.com/SAP/fundamental-styles/pull/3509
- [x] Rating indicator focus issue (Horizon) - https://github.com/SAP/fundamental-styles/pull/3508
Fund-styles:
Should be:
- [x] Select (Horizon) - the focus for the menu elements (first and last element) should be consistent with the Menu and List. https://github.com/SAP/fundamental-styles/pull/3510
Select (Horizon)
Menu (Horizon)
- [x] Horizontal Navigation (Horizon) focus issues: https://github.com/SAP/fundamental-styles/pull/3510
- [x] Select (Horizon) - the focus for the menu elements (first and last element) should be consistent with the Menu and List.
Same issue on multi-input and combobox. I think our official answer is that these fd-lists which are in popover dropdowns actually need to be fd-menu's. The reasoning being that we did not want to couple the list component to the popover. But I think that will require significant changes on both the styles repo and fundamental-ngx
- [x] Progress Indicator - issue when the bar is at 0% (Horizon)
![]()
This can not be solved in CSS
- [x] Progress Indicator - issue when the bar is at 0% (Horizon)
![]()
This can not be solved in CSS
You can use aria-valuenow for value and apply needed styling
- [x] Horizon progress indicator: - https://github.com/SAP/fundamental-styles/pull/3509
100% width is not completely a 100% width:
- [x] Upload collection with long text - save/edit buttons get vertically stacked won't fix
- [x] Breadcrumb does not have an underline on hover https://github.com/SAP/fundamental-styles/pull/3512
- [x] Upload collection with long text - save/edit buttons get vertically stacked
![]()
That's how Platon intended. https://github.com/SAP/fundamental-styles/pull/3227#issuecomment-1076524272
- [x] Breadcrumb does not have an underline on hover
I think breadcrumb link element should go. There is no need for it, that is exactly what fd-link is
- [x] tool header - button edges are cut off https://github.com/SAP/fundamental-styles/pull/3515
- [x] shellbar - popover not aligned (all themes)
- [x] Horizon icon tab bar is missing separators also causing broken focus outline on menu item https://github.com/SAP/fundamental-styles/pull/3518
fiori:
horizon:
- [x] card with list - incorrect focus outline. - https://github.com/SAP/fundamental-styles/pull/3542
- [x] shellbar - popover not aligned (all themes)
![]()
@mikerodonnell89 it is actually aligned. Menu trigger has own paddings. @droshev @InnaAtanasova should we refactor those trigger controls to exclude margins so that popovers would be aligned to the text and not the container?

- [x] Avatar Group, no paddings on dropdown's input https://github.com/SAP/fundamental-styles/pull/3543

- [x] Quick View, no paddings on inputs https://github.com/SAP/fundamental-styles/pull/3543

- [x] Avatar Group, no paddings on dropdown's input
![]()
- [x] Quick View, no paddings on inputs
![]()
These shouldn't even have the fd-input class in my opinion
- [x] Multi Input, outline margins https://github.com/SAP/fundamental-styles/issues/3495#issuecomment-1149148496

@mikerodonnell89 it is actually aligned. Menu trigger has own paddings. @droshev @InnaAtanasova should we refactor those trigger controls to exclude margins so that popovers would be aligned to the text and not the container?
![]()
I think yes for sure
- [ ] Multi Input, outline margins
![]()
So I agree these look a little weird, but they share the same margins as the focus outlines for the other list items and the same border-radius as the parent popover body element. Screenshot below has forced focus on the elements showing that they all do have the same margins
- [x] Object Marker, wrong focus state. In wiki said to use Link's focus designs. https://github.com/SAP/fundamental-styles/pull/3587
