为提升您的使用体验,本站正在维护,部分功能暂时无法使用。如果本站文章无法解决您的问题,您想要向社区提问的话,请到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 提问,我们的支持社区将会很快回复您的疑问。

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

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

  • 3 个回答
  • 7 人有此问题
  • 6 次查看
  • 最后回复者为 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?

被采纳的解决方案

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

定位到答案原位置 👍 0

所有回复 (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

选择的解决方案

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