microsoft / microsoft/BotFramework-WebChat

The transcript randomly loses stickiness to bottom when browser is zoomed out

Open
#4,734 8 comments 1 reaction 1 assignee View on GitHub

@OEvgeny is already working on this.

Since Feb 10, 2025.

Bot Services bug customer-replied-to customer-reported
Dominant language
HTML
Stars
1.8k
Forks
1.6k
Avg merge
22h 58m
Merged PRs (30d)
2

Description

Is it an issue related to Adaptive Cards?

No

Is this an accessibility issue?

No

What version of Web Chat are you using?

Latest production

Which distribution are you using Web Chat from?

NPM

Which hosting environment does this issue primarily affect?

Web apps

Which browsers and platforms do the issue happened?

Browser: Edge (latest), Browser: Chrome (latest)

Which area does this issue affect?

Chat history

What is the public URL for the website?

https://microsoft.github.io/BotFramework-WebChat/06.recomposing-ui/a.minimizable-web-chat/

Please describe the bug

The transcript randomly loses stickiness when browser is zoomed out (80%-90%). Looks like the issue is caused by the browser decreasing the font size and resulting in fractional pixel values; for example, the height of span elements inside activities timestamp is 16.25px.

Do you see any errors in console log?
[NO]
How to reproduce the issue?
  1. Navigate to https://microsoft.github.io/BotFramework-WebChat/06.recomposing-ui/a.minimizable-web-chat/
  2. Zoom in browser
  3. Type "card bingsports" in the send box
  4. Wait for the bot to answer.
  5. Repeat step 2. After 5-10 messages, the bug should reproduce.
What do you expect?

The chat to maintain stickiness.

What actually happened?

Stickiness to bottom is lost.

Do you have any screenshots or recordings to repro the issue?

image

Adaptive Card JSON

No response

Additional context

[BUG]

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.