You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/copilot-instructions.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -256,6 +256,7 @@ Format: `[Component/Feature] Description` (see existing entries for style)
256
256
8.**When reusing an existing component in a new context** (e.g. embedding a component inside a new handler, effect, or renderer), always read the component's existing canonical platform consumer first and replicate **all** of its event subscriptions, lifecycle hooks, and teardown logic. Never assume that rendering the component is sufficient. Components often have additional contracts (update events, binding context propagation, etc.) that only the canonical consumer reveals. Missing these causes silent regressions where the component renders correctly initially but fails to update afterwards.
257
257
9.**Don't** put navigation-row accessibility defaults on the generic `ListItem`. `ListItem` is used for many patterns, including rows with switches or other interactive content. Defaults that make a row expose parent button semantics must be scoped to `NavigationListItem` or another navigation-specific component.
258
258
10.**NavigationListItem accessibility**: The row itself must be the accessibility element and must have the platform Button trait so screen readers announce `"{Title}, Button"` / `"{Title}, knapp"`. Set the semantic description and button trait on the outer `NavigationListItem`, exclude internal visual children from the accessibility tree, and when the item is hosted in a `CollectionView`, propagate the trait to all relevant native cell/content wrappers because the focused accessibility element may be the cell, the cell content view, or the MAUI platform view.
259
+
11.**SystemMessage styles**: When adding Alert-like styling to `SystemMessage`, create dedicated SystemMessage style resources/API based on Alert color tokens. Do not change or refactor existing `AlertStyle`, `AlertStyleResources`, or `AlertTypeStyle` just to support SystemMessage.
259
260
260
261
## Key Files to Reference
261
262
-`API/Builder/AppHostBuilderExtensions.cs` - Library initialization and handler registration
Copy file name to clipboardExpand all lines: CHANGELOG.md
+3Lines changed: 3 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,3 +1,6 @@
1
+
## [61.1.0]
2
+
-[SystemMessage] Added `SystemMessageStyle` support for Alert-based background, text and border colors, border and shadow, fling-to-dismiss, and screen reader announcement.
3
+
1
4
## [61.0.0]
2
5
-[BarcodeScanner]**BREAKING**: Removed `BarcodeScannerStartOptions.DuplicateScanCooldown`. Repeated scans of the same barcode are no longer suppressed after the scanner resumes.
0 commit comments