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

users.sch.gr - The coordinates are different when clicking on the same location on a svg text #135876

Open
webcompat-bot opened this issue Apr 13, 2024 · 1 comment
Labels
browser-firefox engine-gecko The browser uses the Gecko rendering engine priority-normal severity-important A non-core broken piece of functionality, not behaving the way you would expect. status-needsinfo-wisniewskit ping @wisniewskit

Comments

@webcompat-bot
Copy link

webcompat-bot commented Apr 13, 2024

URL: https://users.sch.gr/kodulis/svg_tspan_test.html

Browser / Version: Firefox 124.0
Operating System: Windows 10
Tested Another Browser: Yes Chrome

Problem type: Something else
Description: When mouse is clicking or moving over an "svg tspan" element, the offset coordinates differ from the corresponding if it was just an "svg text" element. This inconsistency does not exist on Chrome, Opera and Edge.
Steps to Reproduce:
I am using Firefox browser version 124.0.2 (64-bit) on a desktop computer.

When mouse is clicking or moving over an "svg tspan" element, the "event.offsetX" and "event.offsetY" coordinates differ from the corresponding if it was just an "svg text" element.
In contrary, the "e.clientX" and "e.clientY" coordinates are the same.

This is not happening on Chrome, Opera and Edge. All these browsers report the same coordinates regardless "tspan" or "text".

I can't say which behavior is correct and which is wrong. But there is an inconsistency.

I made a test page to see the problem.
If you click, for example, on T of the text the offsetX coordinate differs from that if you click on T of the tspan. This is not happening on other browsers.

View the screenshot Screenshot
Browser Configuration
  • None

From webcompat.com with ❤️

@webcompat-bot webcompat-bot added the action-needsmoderation The moderation has not yet been completed label Apr 13, 2024
@webcompat-bot webcompat-bot added this to the needstriage milestone Apr 13, 2024
@webcompat-bot webcompat-bot added the browser-fixme This requires manual assignment for the browser name label Apr 13, 2024
@webcompat-bot webcompat-bot changed the title In the moderation queue. users.sch.gr - see bug description Apr 15, 2024
@webcompat-bot webcompat-bot added browser-firefox priority-normal engine-gecko The browser uses the Gecko rendering engine and removed browser-fixme This requires manual assignment for the browser name action-needsmoderation The moderation has not yet been completed labels Apr 15, 2024
@sv-calin
Copy link

sv-calin commented Apr 15, 2024

Thank you for reporting this issue, I was able to reproduce it. The coordinates are different Firefox vs Chrome:

sch.mp4

Tested on:
• Browser / Version: Firefox Nightly 126.0a1 (2024-04-14) / Firefox Release 124.0.2 / Chrome 123.0.6312.106
• Operating System: Windows 10

Notes:

  1. Reproducible on both Firefox Release and Nightly (regardless of the ETP status)
  2. Not reproducible on Chrome

Moving to Needsdiagnosis.

[qa_16/2024]

@sv-calin sv-calin changed the title users.sch.gr - see bug description users.sch.gr - The coordinates are different when clicking on the same location on a svg text Apr 15, 2024
@sv-calin sv-calin modified the milestones: needstriage, needsdiagnosis Apr 15, 2024
@sv-calin sv-calin added the severity-important A non-core broken piece of functionality, not behaving the way you would expect. label Apr 15, 2024
@denschub denschub added the status-needsinfo-wisniewskit ping @wisniewskit label Apr 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
browser-firefox engine-gecko The browser uses the Gecko rendering engine priority-normal severity-important A non-core broken piece of functionality, not behaving the way you would expect. status-needsinfo-wisniewskit ping @wisniewskit
Projects
None yet
Development

No branches or pull requests

3 participants