Zoom out not working in chrome/brave

[idogrf]

Checklist

• [X] I have updated the card to the latest version available
• [X] I have cleared the cache of my browser
• [X] I have checked if the problem is already reported

The problem

This is a really minor issue

Zooming out of the map using the mouse scroll wheel doesn't work. I've tried using chrome and brave, both on latest version and it doesn't zoom out. Zoom in does work... weird

Tried the same on edge browser and it does work.

What version of a card has described problem?

v2.0.11

What was the last working version card?

No response

What vacuum model do you have problems with?

xiaomi mi robot (1st gen)

Which integration do you use to control your vacuum (link)?

https://www.home-assistant.io/integrations/xiaomi_miio

What browser (browsers/apps) does have this problem?

Chrome/Brave

What version of Home Assistant do you use?

docker

What type of installation are you running?

Home Assistant Container

Card's configuration

type: custom:xiaomi-vacuum-map-card
entity: vacuum.xiaomi_vacuum_cleaner
map_source:
  camera: camera.xiaomi_cloud_map_extractor
calibration_source:
  camera: true
map_modes:
  - template: vacuum_clean_zone_predefined
    predefined_selections:
      - zones: input_text.zone_kitchen
      - zones: input_text.zone_dinning_room
      - zones: input_text.zone_living_room
      - zones: input_text.zone_office
      - zones: input_text.zone_bedroom
      - zones: input_text.zone_hall
      - zones: input_text.zone_toilet
  - template: vacuum_clean_zone
  - template: vacuum_goto

Javascript errors shown in the browser's console (if applicable)

No response

Additional information

No response

[PiotrMachowski]

O.o Is there anything in browser's console?

Can you try if it is still broken in incognito mode?

[idogrf]

Don't see anything out of the ordinary in the console or the logs Same behavior in incognito

Tried switching to a different mouse to see if it's something with Logitech's control software, same behavior

Also tried opening on another laptop, and it seems to be working as expected there So I'm guessing the problem is local on the laptop I'm using... very weird

In any case, this isn't worth a lot of investigating, especially since it seems to only affect my local environment

[PiotrMachowski]

Do you have it wrapped inside a different card, or it's directly in a dashboard? Which version of Chrome do you have?

[idogrf]

no, it's not wrapped, it's directly on the dashboard -

  - title: Vacuum
    path: vacuum
    icon: mdi:broom
    badges: []
    cards:
      - type: custom:xiaomi-vacuum-map-card
        entity: vacuum.xiaomi_vacuum_cleaner
        map_source:
          camera: camera.xiaomi_cloud_map_extractor
        calibration_source:
          camera: true
        map_modes:
          - template: vacuum_clean_zone_predefined
            predefined_selections:
              - zones: input_text.zone_kitchen
              - zones: input_text.zone_dinning_room
              - zones: input_text.zone_living_room
              - zones: input_text.zone_office
              - zones: input_text.zone_bedroom
              - zones: input_text.zone_hall
              - zones: input_text.zone_toilet
          - template: vacuum_clean_zone
          - template: vacuum_goto
      - type: entities
        entities:
          - entity: input_boolean.vacuum_full
          - entity: input_number.vacuum_days_since_full_clean
            name: Days since full clean
          - entity: input_number.vacuum_days_since_office_clean
            name: Days since office clean
      - type: grid
        cards:
          - show_name: true
            show_icon: true
            type: button
            tap_action:
              action: call-service
              service: pyscript.vacuum_map_house
              service_data: {}
              target: {}
            icon: mdi:warehouse
            show_state: false
            name: Map House

chrome version - 103.0.5060.114

[PiotrMachowski]

Do +/-/reset buttons still work?

[idogrf]

yes

[PiotrMachowski]

Does the problem still exist in v2.2.0?

[idogrf]

yea, still have the same issue