Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

En savoir plus

Why does the S-Pen on Galaxy Note 3 move maps when hovering?

  • 3 réponses
  • 7 ont ce problème
  • 6 vues
  • Dernière réponse par guigs

more options

One thing I noticed is that the S-Pen of my Galaxy Note 3 is somehow having a problem. If I use a web side with an embedded map (e.g., Komoot or Google Maps), a hovering S-Pen does already move the map. The normal behaviour in other browser is that I need to press with the S-Pen on the screen before the map is moved. This is a little bit annoying as I use the pen often to navigate on PC web pages. Is this a bug?

One thing I noticed is that the S-Pen of my Galaxy Note 3 is somehow having a problem. If I use a web side with an embedded map (e.g., Komoot or Google Maps), a hovering S-Pen does already move the map. The normal behaviour in other browser is that I need to press with the S-Pen on the screen before the map is moved. This is a little bit annoying as I use the pen often to navigate on PC web pages. Is this a bug?

Solution choisie

HI ruenewald75, Yep, bugzilla.mozilla.org. Might be webcompatibility, but they are generally pretty nice about components.

Some of the expected stuff is found here: https://developer.mozilla.org/en-US/d.../Bug_writing_guidelines

Lire cette réponse dans son contexte 👍 0

Toutes les réponses (3)

more options

Galaxy Note 4 tested with the pen. No it looks like it is expected, as maps also scrolled when I hovered over a test map. The only work around I can think of is to edit the settings for the S-Pen.

more options

guigs2 said

Galaxy Note 4 tested with the pen. No it looks like it is expected, as maps also scrolled when I hovered over a test map. The only work around I can think of is to edit the settings for the S-Pen.

Thanks for testing! So is this then a bug inside firefox? Can I report it into some bug tracking system?

more options

Solution choisie

HI ruenewald75, Yep, bugzilla.mozilla.org. Might be webcompatibility, but they are generally pretty nice about components.

Some of the expected stuff is found here: https://developer.mozilla.org/en-US/d.../Bug_writing_guidelines