microsoft / microsoft/AdaptiveCards

ElementVisibilityChanged event

Open
#1,638 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Area-Inconsistency Area-Renderers Epic Proposal
Dominant language
C#
Stars
2k
Forks
595
Avg merge
1d 19h
Merged PRs (30d)
1

Description

Release Renderer status Tasks status
Not scheduled ๐Ÿ”„ .NET (#842)
โœ”๏ธ Android (#1635)
๐Ÿ”„ iOS (#2464)
โœ”๏ธ TS (#2465)
๐Ÿ”„ UWP (#2466)
โœ”๏ธ Shared (#2463)

The problem

When cards are in a scrolling list, like instant messages, and the user clicks on a ShowCard action, the host needs to know that they should scroll down to show the new card content that appears. Therefore, hosts need an event they can listen to when element visibility has changed, so they know which content they should ensure is in the scroll view.

They can't just listen to the entire size changed events of the card, since if the ShowCard is taller than the height of the viewport, they need to scroll it to the beginning of the ShowCard, so they actually need to know the element itself that was shown to achieve that.

Auto-generated task status

  • Shared
  • .NET
  • Android
  • iOS
  • TS
  • UWP

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up โ€” it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files or tests are named. Start with issue #1638, review the completed Shared, Android, and TS work alongside the incomplete .NET, iOS, and UWP renderer tasks, and determine how the event should expose the element whose visibility changed. Done means the remaining renderers provide that host event for scrolling to the newly shown card content.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, csharp, ios, typescript
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.