docs(cdk-experimental/menu): add initial documentation for cdk menu directives #20412

andy9775 · 2020-08-25T15:21:45Z

No description provided.

andy9775 · 2020-08-25T15:22:36Z

Once approved, a follow up pr to have the actual examples

jelbourn

Can you break lines at 100 characters?

jelbourn · 2020-08-25T17:33:35Z

src/cdk-experimental/menu/menu.md

@@ -0,0 +1,167 @@
+The `@angular/cdk-experimental/menu` module provides you with a way to easily create complex menu interfaces with support for:


Suggested change

The `@angular/cdk-experimental/menu` module provides you with a way to easily create complex menu interfaces with support for:

The `@angular/cdk-experimental/menu` module provides directive to help create custom menu interactions based on the [WAI ARIA specification](https://www.w3.org/TR/wai-aria-1.1/).

jelbourn · 2020-08-25T17:34:11Z

src/cdk-experimental/menu/menu.md

+- Standalone Menus
+- Menubars
+- Context Menus
+- Inline Menus
+- MenuItems
+- RadioButtonItems
+- CheckboxItems


I would break this into a section called "Supported ARIA roles" and use the role names from the spec, combining with some of the text you have below.

jelbourn · 2020-08-25T17:35:39Z

src/cdk-experimental/menu/menu.md

+`@angular/cdk-experimental/menu` can also intelligently predict if a user is attempting to navigate to an open submenu and prevent premature closeouts.
+


I would move this to its own section named something like "Smart menu aim" that outlines what it does (potentially with a diagram) and a very brief explanation of how it works.

jelbourn · 2020-08-25T17:38:45Z

src/cdk-experimental/menu/menu.md

+Keep in mind that there are two important requirements which must be kept in mind when building menus:
+
+First, a triggering component, or a component inside of a `CdkMenu` or `CdkMenuBar`, must have the `cdkMenuItem` directive like so,


Suggested change

Keep in mind that there are two important requirements which must be kept in mind when building menus:

First, a triggering component, or a component inside of a `CdkMenu` or `CdkMenuBar`, must have the `cdkMenuItem` directive like so,

Most menu interactions consist of two parts: a trigger and a menu panel.

#### Triggers

(talk about buttons and menu-bars here)

#### Menu panels

(talk about cdkMenuPanel here)

jelbourn · 2020-08-25T17:40:45Z

src/cdk-experimental/menu/menu.md

+
+<!-- TODO inline menu example (gmail buttons?) -->
+
+### Menuitem


Suggested change

### Menuitem

### Menu items

(similar for other headers)

jelbourn · 2020-08-25T17:41:30Z

src/cdk-experimental/menu/menu.md

+
+<!-- TODO standalone menu example with checkboxes and grouped radios -->
+
+### Accessability


Suggested change

### Accessability

### Accessibility

jelbourn · 2020-08-25T17:42:30Z

src/cdk-experimental/menu/menu.md

+[1]: https://www.w3.org/TR/wai-aria-practices-1.1/#menu 'Aria Menubar Pattern'
+[2]: https://www.w3.org/TR/wai-aria-practices-1.1/#keyboard-interaction-12 'Aria Menubar Keyboard Interaction'


I'm trying to get away from using numbered links now and instead using links with names, e.g.

Suggested change

[1]: https://www.w3.org/TR/wai-aria-practices-1.1/#menu 'Aria Menubar Pattern'

[2]: https://www.w3.org/TR/wai-aria-practices-1.1/#keyboard-interaction-12 'Aria Menubar Keyboard Interaction'

[menubar]: https://www.w3.org/TR/wai-aria-practices-1.1/#menu 'Aria Menubar Pattern'

[keyboard]: https://www.w3.org/TR/wai-aria-practices-1.1/#keyboard-interaction-12 'Aria Menubar Keyboard Interaction'

andy9775 · 2020-08-25T19:13:17Z

@jelbourn feedback should be addressed

teflonwaffles · 2020-08-25T20:38:03Z

src/cdk-experimental/menu/menu.md

+now add the various directives in order to build out your menu. A basic standalone menu consists of
+the following directives:
+
+- `cdkMenuItem` - added to the button itself


Which button? (There's talk of multiple buttons here.)

teflonwaffles · 2020-08-25T20:44:32Z

src/cdk-experimental/menu/menu.md

+
+<!-- TODO basic context menu example -->
+
+Context menu triggers may be nested within parent contexts and when a user right clicks, the deepest


This could be clearer. 'Nested components can have context menu triggers at each level. When a user right clicks, the menu associated with the deepest component the user is hovering over is opened up.'

teflonwaffles · 2020-08-25T20:46:25Z

src/cdk-experimental/menu/menu.md

+
+### Inline Menus
+
+Inline menus are groups of menu items which typically do not trigger their own menus and the menu


This could also be clearer -- emphasize that the menu doesn't 'pop up', but all menu items are displayed from the start.

teflonwaffles · 2020-08-25T20:47:42Z

src/cdk-experimental/menu/menu.md

+### Inline Menus
+
+Inline menus are groups of menu items which typically do not trigger their own menus and the menu
+items implement some type of on-click behavior. The benefit of using an inline menu over a group of


'implement some type of on-click behavior' should be clear enough that you can omit it. (You say from the start that these are groups of menu items, which usually have on-click behavior.)

During our feedback session some thought that a trigger can open a submenu when placed inline. I want to emphasize that it shouldn't be the case.

teflonwaffles · 2020-08-25T20:48:59Z

src/cdk-experimental/menu/menu.md

+```html
+<ng-template cdkMenuPanel #panel="cdkMenuPanel">
+  <div cdkMenu [cdkMenuPanel]="panel">
+    <button cdkMenuItem [cdkMenuItemTriggered]="closeApp()">Close</button>


Should this be (cdkMenuItemTriggered), instead of [...]? (If not, this is noteworthy, and should be explained -- with a TODO to switch to the regular style.)

Good catch! It should use parentheses

teflonwaffles · 2020-08-25T20:50:45Z

src/cdk-experimental/menu/menu.md

+```
+
+Note however that when the menu is closed and reopened any state is lost. You must subscribe to the
+groups `change` output, or to `cdkMenuItemToggled` on each radio item and track changes your self.


How do you specify which item should be checked to start?

There's a checked input - I'll add that to the doc.

teflonwaffles · 2020-08-25T20:51:19Z

src/cdk-experimental/menu/menu.md

+![menu aim diagram][diagram]
+
+As demonstrated in the diagram above we first track the users mouse movements within a menu. Next,
+when a user mouses into a sibling menu item (e.g. Share button) the sibling item asks the Menu Aim


"user's mouse movements"

teflonwaffles · 2020-08-25T20:52:18Z

src/cdk-experimental/menu/menu.md

+user is moving towards the submenu and we shouldn't close out. Finally, as the user mouses into
+other sibling triggers, as long as the slope of the current mouse movement is steeper than the
+previous, it assumes that the user is moving towards the submenu. Users however may sometimes stop
+short in a sibling item after moving towards the submenu therefore the service is intelligent enough


This is a bit of a run-on sentence.

andy9775 · 2020-08-25T21:24:51Z

@teflonwaffles feedback should be addressed

jelbourn

Mostly suggestions for passive voice and brevity here without substantively affecting content or organization

jelbourn · 2020-08-26T19:53:19Z

src/cdk-experimental/menu/menu.md

+interaction. Further, all directives apply their associated aria roles to the component they are
+added to.
+
+### Supported Aria Roles


Suggested change

### Supported Aria Roles

### Supported ARIA Roles

nit: aria is an acronym

jelbourn · 2020-08-26T22:43:41Z

src/cdk-experimental/menu/menu.md

+The directives provided by `@angular/cdk-experimental/menu` automatically provide the related roles
+for each component they are placed on.


Suggested change

The directives provided by `@angular/cdk-experimental/menu` automatically provide the related roles

for each component they are placed on.

The directives in `@angular/cdk-experimental/menu` set the appropriate roles

on their host element.

tweaks for brevity

jelbourn · 2020-08-26T22:49:44Z

src/cdk-experimental/menu/menu.md

+Start by importing the `CdkMenuModule` into the `NgModule` where you want to create menus. You can
+now add the various directives in order to build out your menu. A basic standalone menu consists of
+the following directives:


Suggested change

Start by importing the `CdkMenuModule` into the `NgModule` where you want to create menus. You can

now add the various directives in order to build out your menu. A basic standalone menu consists of

the following directives:

Import the `CdkMenuModule` into the `NgModule` in which you want to create menus. You can

then apply menu directives to build your custom menu. A typical menu consists of the following directives:

jelbourn · 2020-08-26T22:50:08Z

src/cdk-experimental/menu/menu.md

+- `cdkMenuItem` - added to each button
+- `cdkMenuTriggerFor` - links a trigger button to a menu you intend to open
+- `cdkMenuPanel` - wraps the menu and provides a link between the `cdkMenuTriggerFor` and the
+  `cdkMenu`
+- `cdkMenu` - the actual menu you want to open


I would list in the order: trigger, panel, menu, item

jelbourn · 2020-08-26T22:51:23Z

src/cdk-experimental/menu/menu.md

+
+#### Triggers
+
+A triggering component must have the `cdkMenuItem` and `cdkMenuTriggerFor` directives like so,


cdkMenuItem isn't supposed to be required for just a regular button

A trigger does need cdkMenuItem, also if you don't add cdkMenuItem to a regular button keyboard navigation won't work as expected - I'll make that clear.

jelbourn · 2020-08-27T01:44:58Z

src/cdk-experimental/menu/menu.md

+
+### Smart Menu Aim
+
+`@angular/cdk-experimental/menu` can also intelligently predict if a user is attempting to navigate


Suggested change

`@angular/cdk-experimental/menu` can also intelligently predict if a user is attempting to navigate

`@angular/cdk-experimental/menu` intelligently predicts when a user intends to navigate

nit: some passive voice, brevity

jelbourn · 2020-08-27T01:45:36Z

src/cdk-experimental/menu/menu.md

+
+`@angular/cdk-experimental/menu` can also intelligently predict if a user is attempting to navigate
+to an open submenu and prevent premature closeouts. This functionality prevents users from having to
+hunt through the open menus in a maze-like fashion in order to get to their destination.


Suggested change

hunt through the open menus in a maze-like fashion in order to get to their destination.

hunt through the open menus in a maze-like fashion to reach their destination.

jelbourn · 2020-08-27T01:46:41Z

src/cdk-experimental/menu/menu.md

+By default `cdkMenu` acts as a group for `cdkMenuItemRadio` elements. That is, components marked
+with `cdkMenuItemRadio` added as children of a `cdkMenu` will be logically grouped and only a single
+component can have the checked state.


Suggested change

By default `cdkMenu` acts as a group for `cdkMenuItemRadio` elements. That is, components marked

with `cdkMenuItemRadio` added as children of a `cdkMenu` will be logically grouped and only a single

component can have the checked state.

By default `cdkMenu` acts as a group for `cdkMenuItemRadio` elements. Elements

with `cdkMenuItemRadio` added as children of a `cdkMenu` will be logically grouped and only a single

item can have the checked state.

jelbourn · 2020-08-27T01:48:53Z

src/cdk-experimental/menu/menu.md

+A `cdkMenuItemRadio` behaves as you would expect a radio button to behave. A use case may be
+toggling through more than one state since radio buttons can be grouped together. A component with
+the `cdkMenuItemRadio` directive does not need the additional `cdkMenuItem` directive.
+


Suggested change

A `cdkMenuItemRadio` behaves as you would expect a radio button to behave. A use case may be

toggling through more than one state since radio buttons can be grouped together. A component with

the `cdkMenuItemRadio` directive does not need the additional `cdkMenuItem` directive.

A `cdkMenuItemRadio` is a special type of menuitem that behaves as a radio button. You

can use this type of menuitem for menus with exclusively selectable items.

I think leaving A component with the cdkMenuItemRadiodirective does not need the additionalcdkMenuItem directive. is worth it. Thoughts?

Here and for checkbox

jelbourn · 2020-08-27T01:50:10Z

src/cdk-experimental/menu/menu.md

+A component with the `cdkMenuItemCheckbox` directive behaves just as you would expect a typical
+checkbox to behave. A use case may be toggling an independent setting since it contains a checked
+state. A component with the `cdkMenuItemCheckbox` directive does not need the additional
+`cdkMenuItem` directive.


Suggested change

A component with the `cdkMenuItemCheckbox` directive behaves just as you would expect a typical

checkbox to behave. A use case may be toggling an independent setting since it contains a checked

state. A component with the `cdkMenuItemCheckbox` directive does not need the additional

`cdkMenuItem` directive.

A `cdkMenuItemCheckbox` is a special type of menuitem that behaves as a checkbox. You

can use this type of menuitem to toggle items on and off.

andy9775 · 2020-08-27T14:06:11Z

@jelbourn feedback should be addressed. I also took another run through and changed some passive to active voice so please take a look through again.

jelbourn

Okay, I think this is my last set of comments

jelbourn · 2020-08-27T17:09:18Z

src/cdk-experimental/menu/menu.md

+
+The `CdkMenuBar` directive follows the [ARIA menubar][menubar] spec and behaves similar to a desktop
+app menubar. It consists of at least one `CdkMenuItem` which triggers a submenu. A menubar can be
+layed out horizontally or vertically (defaulting to horizontal). If the style is changed, you must


Suggested change

layed out horizontally or vertically (defaulting to horizontal). If the style is changed, you must

layed out horizontally or vertically (defaulting to horizontal). If the layout changes, you must

jelbourn · 2020-08-27T17:13:09Z

src/cdk-experimental/menu/menu.md

+The primary difference between a menubar and a standalone menu is the menubar groups together the
+triggering components. Therefore, menus in a menubar can be opened/closed when hovering between
+their triggers and keyboard navigation listens to left and right arrow buttons which toggles between
+the menu items in the menubar.


I'm not sure this bit is strictly necessary, since I think the difference between a menubar and a standalone menu (just a button) is readily apparent.

jelbourn · 2020-08-27T17:16:44Z

src/cdk-experimental/menu/menu.md

+A context menu opens when a user right-clicks within some container element. A context is an area of
+your application which contains some content where you want to open up a menu. When a user
+right-clicks within the context the associated menu opens up next to their cursor - as you would
+expect with a typical right click menu.


Suggested change

A context menu opens when a user right-clicks within some container element. A context is an area of

your application which contains some content where you want to open up a menu. When a user

right-clicks within the context the associated menu opens up next to their cursor - as you would

expect with a typical right click menu.

A context menu opens when a user right-clicks within some container element. You can

mark a container element with the `cdkContextMenuTriggerFor`, which behaves like

`cdkMenuTriggerFor` except that it responds to the browser's native `contextmenu` event.

Custom context menus appear next to the cursor, similarly to native context menus.

jelbourn · 2020-08-27T17:17:45Z

src/cdk-experimental/menu/menu.md

+Nested container elements can have context menu triggers at each level. When a user right-clicks,
+the menu associated with the closest container element opens.


Suggested change

Nested container elements can have context menu triggers at each level. When a user right-clicks,

the menu associated with the closest container element opens.

You can nest context menu container elements. Upon right-click,

the menu associated with the closest container element will open.

jelbourn · 2020-08-27T17:19:10Z

src/cdk-experimental/menu/menu.md

+#### Menu Item Checkboxes
+
+A `cdkMenuItemCheckbox` is a special type of menuitem that behaves as a checkbox. You can use this
+type of menuitem to toggle items on and off. A component with the `cdkMenuItemCheckbox` directive


Suggested change

type of menuitem to toggle items on and off. A component with the `cdkMenuItemCheckbox` directive

type of menuitem to toggle items on and off. An element with the `cdkMenuItemCheckbox` directive

jelbourn · 2020-08-27T17:19:19Z

src/cdk-experimental/menu/menu.md

+#### Menu Item Radios
+
+A `cdkMenuItemRadio` is a special type of menuitem that behaves as a radio button. You can use this
+type of menuitem for menus with exclusively selectable items. A component with the


Suggested change

type of menuitem for menus with exclusively selectable items. A component with the

type of menuitem for menus with exclusively selectable items. An element with the

jelbourn · 2020-08-27T18:35:57Z

src/cdk-experimental/menu/menu.md

+By using `@angular/cdk-experimental/menu` you get all of the expected behaviors following the ARIA
+best practices including consideration for left-to-right and right-to-left layouts, and accessible
+interaction. Further, all directives apply their associated ARIA roles to the component they are
+added to.


Suggested change

By using `@angular/cdk-experimental/menu` you get all of the expected behaviors following the ARIA

best practices including consideration for left-to-right and right-to-left layouts, and accessible

interaction. Further, all directives apply their associated ARIA roles to the component they are

added to.

By using `@angular/cdk-experimental/menu` you get all of the expected behaviors for an accessible experience, including bidi layout support, keyboard interaction, and focus management. All directives apply their associated ARIA roles to their host element.

jelbourn · 2020-08-27T18:39:06Z

src/cdk-experimental/menu/menu.md

+
+### Accessibility
+
+The set of directives defined in `@angular/cdk-experimental/menu` follow accessability best


Suggested change

The set of directives defined in `@angular/cdk-experimental/menu` follow accessability best

The set of directives defined in `@angular/cdk-experimental/menu` follow accessibility best

jelbourn · 2020-08-27T18:39:55Z

src/cdk-experimental/menu/menu.md

+practices as defined in the [ARIA spec][menubar]. Specifically, the menus are aware of left-to-right
+and right-to-left layouts and opened appropriately. You should however add any necessary CSS styles.
+Menu items should always have meaningful labels, whether through text content, `aria-label`, or
+`aria-labelledby` Finally, keyboard interaction is supported as defined in the [ARIA menubar


Suggested change

`aria-labelledby` Finally, keyboard interaction is supported as defined in the [ARIA menubar

`aria-labelledby`. Finally, keyboard interaction is supported as defined in the [ARIA menubar

…irectives

andy9775 · 2020-08-27T23:08:30Z

@jelbourn Feedback should be addressed

jelbourn

LGTM

…irectives (angular#20412)

angular-automatic-lock-bot · 2020-09-28T00:10:50Z

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}

andy9775 requested a review from jelbourn as a code owner August 25, 2020 15:21

googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Aug 25, 2020

andy9775 requested a review from teflonwaffles August 25, 2020 15:21

jelbourn added the target: minor This PR is targeted for the next minor release label Aug 25, 2020

jelbourn reviewed Aug 25, 2020

View reviewed changes

andy9775 force-pushed the cdk-menu-docs branch from ee003ef to 5c16dc3 Compare August 25, 2020 19:13

teflonwaffles reviewed Aug 25, 2020

View reviewed changes

andy9775 force-pushed the cdk-menu-docs branch from 5c16dc3 to f59573d Compare August 25, 2020 21:24

jelbourn reviewed Aug 27, 2020

View reviewed changes

andy9775 force-pushed the cdk-menu-docs branch from f59573d to f26382f Compare August 27, 2020 14:05

jelbourn reviewed Aug 27, 2020

View reviewed changes

docs(cdk-experimental/menu): add initial documentation for cdk menu d…

85ed9b6

…irectives

andy9775 force-pushed the cdk-menu-docs branch from f26382f to 85ed9b6 Compare August 27, 2020 23:08

jelbourn approved these changes Aug 28, 2020

View reviewed changes

jelbourn added action: merge The PR is ready for merge by the caretaker merge safe labels Aug 28, 2020

jelbourn merged commit 4f1238f into angular:master Aug 28, 2020

annieyw pushed a commit to annieyw/components that referenced this pull request Aug 31, 2020

docs(cdk-experimental/menu): add initial documentation for cdk menu d…

27cb572

…irectives (angular#20412)

mmalerba pushed a commit to mmalerba/components that referenced this pull request Sep 5, 2020

docs(cdk-experimental/menu): add initial documentation for cdk menu d…

737ff4a

…irectives (angular#20412)

angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 28, 2020

		@@ -0,0 +1,167 @@
		The `@angular/cdk-experimental/menu` module provides you with a way to easily create complex menu interfaces with support for:

		`@angular/cdk-experimental/menu` can also intelligently predict if a user is attempting to navigate to an open submenu and prevent premature closeouts.

		Keep in mind that there are two important requirements which must be kept in mind when building menus:

		First, a triggering component, or a component inside of a `CdkMenu` or `CdkMenuBar`, must have the `cdkMenuItem` directive like so,

-Keep in mind that there are two important requirements which must be kept in mind when building menus:
-First, a triggering component, or a component inside of a `CdkMenu` or `CdkMenuBar`, must have the `cdkMenuItem` directive like so,
+Most menu interactions consist of two parts: a trigger and a menu panel.
+#### Triggers
+(talk about buttons and menu-bars here)
+#### Menu panels
+(talk about cdkMenuPanel here)


		<!-- TODO inline menu example (gmail buttons?) -->

		### Menuitem


		<!-- TODO standalone menu example with checkboxes and grouped radios -->

		### Accessability

		[1]: https://www.w3.org/TR/wai-aria-practices-1.1/#menu 'Aria Menubar Pattern'
		[2]: https://www.w3.org/TR/wai-aria-practices-1.1/#keyboard-interaction-12 'Aria Menubar Keyboard Interaction'


		<!-- TODO basic context menu example -->

		Context menu triggers may be nested within parent contexts and when a user right clicks, the deepest


		### Inline Menus

		Inline menus are groups of menu items which typically do not trigger their own menus and the menu

		The directives provided by `@angular/cdk-experimental/menu` automatically provide the related roles
		for each component they are placed on.


		#### Triggers

		A triggering component must have the `cdkMenuItem` and `cdkMenuTriggerFor` directives like so,


		### Smart Menu Aim

		`@angular/cdk-experimental/menu` can also intelligently predict if a user is attempting to navigate

	`@angular/cdk-experimental/menu` can also intelligently predict if a user is attempting to navigate
	`@angular/cdk-experimental/menu` intelligently predicts when a user intends to navigate

	hunt through the open menus in a maze-like fashion in order to get to their destination.
	hunt through the open menus in a maze-like fashion to reach their destination.

	layed out horizontally or vertically (defaulting to horizontal). If the style is changed, you must
	layed out horizontally or vertically (defaulting to horizontal). If the layout changes, you must

		Nested container elements can have context menu triggers at each level. When a user right-clicks,
		the menu associated with the closest container element opens.

	type of menuitem to toggle items on and off. A component with the `cdkMenuItemCheckbox` directive
	type of menuitem to toggle items on and off. An element with the `cdkMenuItemCheckbox` directive

	type of menuitem for menus with exclusively selectable items. A component with the
	type of menuitem for menus with exclusively selectable items. An element with the


		### Accessibility

		The set of directives defined in `@angular/cdk-experimental/menu` follow accessability best

	`aria-labelledby` Finally, keyboard interaction is supported as defined in the [ARIA menubar
	`aria-labelledby`. Finally, keyboard interaction is supported as defined in the [ARIA menubar

docs(cdk-experimental/menu): add initial documentation for cdk menu directives #20412

docs(cdk-experimental/menu): add initial documentation for cdk menu directives #20412

Uh oh!

Conversation

andy9775 commented Aug 25, 2020

Uh oh!

andy9775 commented Aug 25, 2020

Uh oh!

jelbourn left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

andy9775 commented Aug 25, 2020

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

andy9775 commented Aug 25, 2020

Uh oh!

jelbourn left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

andy9775 commented Aug 27, 2020

Uh oh!