Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Topic Message Viewer Update Behavior #287

Open
1 task done
derek1ee opened this issue Sep 24, 2024 · 0 comments
Open
1 task done

Topic Message Viewer Update Behavior #287

derek1ee opened this issue Sep 24, 2024 · 0 comments
Assignees
Labels
usability References an inability to easily use a feature of the extension

Comments

@derek1ee
Copy link
Contributor

derek1ee commented Sep 24, 2024

Code of Conduct

  • I agree to follow this project's Code of Conduct

On what operating system are you seeing the problem?

macOS (Apple/arm64)

VS Code version

Version: 1.93.1 (Universal)
Commit: 38c31bc77e0dd6ae88a4e9cc93428cc27a56ba40
Date: 2024-09-11T17:20:05.685Z
Electron: 30.4.0
ElectronBuildId: 10073054
Chromium: 124.0.6367.243
Node.js: 20.15.1
V8: 12.4.254.20-electron.0
OS: Darwin arm64 22.6.0

Version of Confluent extension

v0.16.3

To Reproduce

  1. Install, sign into CC, and open a topic message viewer with message constantly coming in.
  2. Observe the behavior of the table showing messages

Current vs. Expected behavior

  1. When staying on the first page (to look at latest messages), the messages keeps scrolling/getting updated. So If I'm trying to copy a value, it's impossible to do on the table because the message will soon be gone and selection will be for some other message. Also select a particular message to view it's full content (which is needed in order to copy because what's previously mentioned), one would need to double click within a second or else it will be scrolled away.
  2. Same goes for when viewing messages in say page 10. It always shows the latest 900-1000 messages. With messages keep arriving, it means the view constantly change.

Maybe consider a "sticky" behavior, where if a message is highlighted, the view is "locked/anchored" to that message. So that as new messages arrive, the selected message is kept in view, but rather the current page is updated as necessary, because that message will be on page 1 to begin with, but later on page 10, 20, etc.

Relevant log output

No response

Which area(s) are affected? (Select all that apply)

Topics

Additional context

No response

@derek1ee derek1ee added the bug Something isn't working label Sep 24, 2024
@alexeyraspopov alexeyraspopov self-assigned this Sep 24, 2024
@alexeyraspopov alexeyraspopov added usability References an inability to easily use a feature of the extension and removed bug Something isn't working labels Oct 4, 2024
@rhauch rhauch added this to the 2024 Q4 General Improvements milestone Oct 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
usability References an inability to easily use a feature of the extension
Projects
None yet
Development

No branches or pull requests

3 participants