microsoft / microsoft/WindowsAppSDK

Overlapping text in toast with header created in a collection

Open
#4,026 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area-Notifications bug needs-triage
Dominant language
C++
Stars
4.7k
Forks
471
Avg merge
3d 13h
Merged PRs (30d)
28

Description

Describe the bug

When creating a toast in a collection. Windows automatically adds a textual note "via Notification Visualizer" (name of the application).
When the toast contains a header. The same textual note "via..." is added on top of the header text. This makes it very difficult to read the header text.

Steps to reproduce the bug
  1. Start Notification Visualizer app
  2. Create a "sample" collection
  3. Create a toast with the following
<toast>
  <header id="6289" title="Test header" arguments="header"/>
  <visual>
    <binding template="ToastGeneric">
      <text>This is a simple toast message</text>
      <text>With a header in a collection</text>
    </binding>
  </visual> 
</toast>
  1. pop it
Expected behavior

Header text is fully visible and not overwritten.

Screenshots

image

NuGet package version

None

Windows version

Windows 11 (22H2): Build 22621, Windows 10 (21H2): Build 19044

Additional context

No response

Contributor guide

No contributing guide indexed for this repository

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

Start by reproducing the toast from a sample collection in the Notification Visualizer app on the Windows versions listed, using the XML from the report. Compare the rendered header with the expected behavior and verify that the header text is fully visible without the application note overwriting it.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.