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

[Maps][Meta] Usability issues on LAYERS and the layer config modal flyouts #122960

Closed
Tracked by #154870
monfera opened this issue Jan 13, 2022 · 5 comments
Closed
Tracked by #154870
Labels
design discuss Feature:Maps impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:large Large Level of Effort Team:Presentation Presentation Team for Dashboard, Input Controls, and Canvas usability

Comments

@monfera
Copy link
Contributor

monfera commented Jan 13, 2022

Kibana version:
8

1. LAYERS panel flies left and right, when the layer config sidebar comes and goes
A UI principle is that hotspots, buttons and other affordances are not supposed to fly out from underneath the user's pointer on activation. Right now, when clicking the little pencil icon, the entire LAYERS panel flies away from underneath the pointer
Irrespective of this, and the current jank (see below) it is jarring to see the panel fly left and right anyway.

2. LAYERS panel fly is tweened in one direction but sudden in the other
It should be consistent. It doesn't feel like the difference in behavior is due to more jank in one direction than in the other, but maybe it is

3. UI and sometimes the entire browser (tab switch etc.) are blocked for several seconds after common interactions
Clicking on the little pencil will elicit the flyout of the right sidebar layer config panel. It moves/resizes the actual map view, which I think is the culprit. A consequence is that even when the user gets a jankily sliding out config panel, not even the scrolling of the sidebar works, for numerous seconds. Other things are blocked too. Suggested solution: such interactions should not resize/alter the actual map layer. Mapbox/Maplibre are rather heavy and expensive components so the jank/freeze cost isn't even commensurate with the actual rendering task. Let's talk if someone is on the opinion that blocking the UI this way is still OK UX

4. Easy loss of layer config changes
Steps to reproduce:

  1. Painstakingly configure a layer
  2. Multitask: fill a gh report, check out weather.com etc
  3. Come back and absent-mindedly make the config sidebar go away with the bottom left button (which surely says Cancel but it'd be nice to ask for user confirmation to help avoid lost config)
    An alternative is that instead of our heavy (and to me, ill understood) adherence to the "Apply/Cancel" pattern, we'd have proper undo/redo
@monfera monfera added bug Fixes for quality problems that affect the customer experience discuss [Deprecated-Use Team:Presentation]Team:Geo Former Team Label for Geo Team. Now use Team:Presentation triage_needed design labels Jan 13, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-gis (Team:Geo)

@nreese
Copy link
Contributor

nreese commented Jan 13, 2022

@monfera Thanks for suggesting some usability issues. Do you have any suggestions on ways to avoid these issues?

@nreese nreese removed bug Fixes for quality problems that affect the customer experience triage_needed labels Jan 18, 2022
@nreese
Copy link
Contributor

nreese commented Jan 18, 2022

I removed the bug label and will keep the issue open for a while to see if it sparks conversations and possible solutions.

@teresaalvarezsoler teresaalvarezsoler added impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:large Large Level of Effort labels Jul 21, 2022
@jb1b84 jb1b84 added Feature:Maps Team:Presentation Presentation Team for Dashboard, Input Controls, and Canvas and removed [Deprecated-Use Team:Presentation]Team:Geo Former Team Label for Geo Team. Now use Team:Presentation labels Nov 3, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-presentation (Team:Presentation)

@ThomThomson
Copy link
Contributor

In order to provide better transparency of priorities, issues that will not be prioritized within the next 24 months are being closed.
Tracking request in Maps ice box #154870

@ThomThomson ThomThomson closed this as not planned Won't fix, can't repro, duplicate, stale May 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
design discuss Feature:Maps impact:low Addressing this issue will have a low level of impact on the quality/strength of our product. loe:large Large Level of Effort Team:Presentation Presentation Team for Dashboard, Input Controls, and Canvas usability
Projects
None yet
Development

No branches or pull requests

6 participants