Conversation
| ## Timer Property | ||
| * `"timer" : number` | ||
| * when set, the number sets the duration before a Carousel page transitions to the next Carousel page. | ||
| * while hovering, mouse click, and touch events, this auto transition is canceled. |
There was a problem hiding this comment.
Will the timer start again after the manual transition has been completed?
|
|
||
| This will enable them to show a chat as a group chat in a messenger app. | ||
| #### Key Features | ||
| * Stack a maximum of 2 images. The green status indicator would not be displayed. |
There was a problem hiding this comment.
Is there a reason for displaying only 2 images?
3 and more could be displayed in a slightly different fashion (similar to Teams?)
There was a problem hiding this comment.
No, this is client specific feature. we are going to share this spec with Team to expand the spec further.
| So here we have a sample carousel card. You'll probably notice the ominously-named `TBD` property right away -- we haven't come up with a name for it yet. At any rate, this property is an object containing a `type` property describing what type of card this is. Other properties in this object can be provided to configure behaviors of this type of card (in this example, the timer to use for automatically flipping through the items in a carousel). | ||
|
|
||
| You'll probably also notice the new `CarouselPage` element. It acts pretty similarly to a `Container`, but with some differences: | ||
| So here we have a sample carousel card. You'll probably notice the new `CarouselPage` element. It acts pretty similarly to a `Container`, but with some differences: |
| * We don't allow every element type within a `CarouselPage`, only the subset we decide on (see following sections for more details) | ||
|
|
||
| Having this new element also has the advantage of allowing us to reuse it later should we decide to promote the idea of `Carousel` as a regular page element (a `Carousel` would be a collection of `CarouselPage`s in this regime, though we'd need to decide how to reconcile `TBD` against per-`Carousel` settings). | ||
| Having this new element also has the advantage of allowing us to reuse it later should we decide to promote the idea of `Carousel` as a regular page element (a `Carousel` would be a collection of `CarouselPage`s in this regime. |
| * We don't allow every element type within a `CarouselPage`, only the subset we decide on (see following sections for more details) | ||
|
|
||
| Having this new element also has the advantage of allowing us to reuse it later should we decide to promote the idea of `Carousel` as a regular page element (a `Carousel` would be a collection of `CarouselPage`s in this regime, though we'd need to decide how to reconcile `TBD` against per-`Carousel` settings). | ||
| Having this new element also has the advantage of allowing us to reuse it later should we decide to promote the idea of `Carousel` as a regular page element (a `Carousel` would be a collection of `CarouselPage`s in this regime. |
|
|
||
| This will enable them to show a chat as a group chat in a messenger app. | ||
| #### Key Features | ||
| * Stack a maximum of 2 images. The green status indicator would not be displayed. |
| * `style`: "stacked" | ||
| * indicates that images are displayed in a stack | ||
| * `offset`: a number | ||
| * indicates the magnitude of offset in pixels. This is how far apart diagonally the images are at. Images are at tangent at 0. In other word, there will be no space between the images except the border. Negative values moves images closer up to the image's diameter. Positive values move images farther and there is no limitation imposed by the spec, but will result in bad UI with extreme value. |
There was a problem hiding this comment.
is there some way to specify size of the stacked on top of the other image or is the stacked image always a certain size?
| |Capability|Priority| | ||
| |---|---| | ||
| |Allow users to stack at least 2 images |p0 | ||
| |The stacked image sets support "style": "person" so they are rounded|p0 |
There was a problem hiding this comment.
sorry, I don't see the extra tab.
| |---|---| | ||
| |Allow users to stack at least 2 images |p0 | ||
| |The stacked image sets support "style": "person" so they are rounded|p0 | ||
| |The stacked images stack diagonally with the front image on the left |p0 |
|
Hi @jwoo-msft. This pull request has had no recent activity for the past 5 days . Please take the necessary actions (review, address feedback or commit if reviewed already) to move this along. |
Related Issue
N/A
Description
Updated Carousel and ImageSet design discussion docs for v-team spec review.
Sample Card
N/A
How Verified
N/A
Microsoft Reviewers: Open in CodeFlow