807121 - Drag events on SVG objects in Raphael JS don't work

Status: RESOLVED INCOMPLETE

(Web Compatibility :: Site Reports, defect)

Description

[Jason Ng]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:18.0) Gecko/18.0 Firefox/18.0
Build ID: 20121030042010

Steps to reproduce:

Clicked and dragged on a SVG object created by the framework Raphael JS.  Such as the dots located at: http://raphaeljs.com/curver.html an example page of it in action.


Actual results:

Nothing happened, now events where fired.


Expected results:

There should have being some event fired that would have triggered, something to respond in Raphael JS.  I've tried using a function for my own project that uses the framework, and it also didn't work.

Comment 1

[Kevin Brosnan [Ex-Mozilla]]

This is only broken on 18. It works in 17 and works on 19. Need a regression range for the fix and or break.

Comment 2

[Alice0775 White]

This was regressed by Bug 726615.And this was fixed by Bug 798821.

And It works in Aurora18.0a2 2012-10-31.
http://hg.mozilla.org/releases/mozilla-aurora/rev/2b2d7457e130
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:18.0) Gecko/18.0 Firefox/18.0 ID:20121031042011

Comment 3

[bhavana bajaj [:bajaj]]

Not tracking for release based on comment 2

Comment 4

[Jim Mathies [:jimm]]

Still present if you have touch capable hardware. Moving this over to the evang. bug.

Comment 5

[Kartikaya Gupta (email:[e-mail])]

Page has moved, but the issue is still present - you can't use the mouse to drag the points if touch is enabled. Same thing happens in Chrome. Touch-dragging works fine if touch is enabled.

Comment 6

[Karl Dubost💡 :karlcow]

Switching to needsdiagnosis
This requires an analysis of where and how the issue is happening. 
And suggest a fix in the code before attempting any contacts.

Comment 7

[Mike Taylor [:miketaylr]]

So... there's been a PR open for 4 years to fix this issue: https://github.com/DmitryBaranovskiy/raphael/pull/813/files

It seems like RaphaelJS is unmaintained, I don't have hopes for this getting fixed. If anybody needs to fix this themselves, they can manually apply the patches. Sucks... but I don't see any movement here. I did ask a question in the PR, so if they want to fix it, we can re-open.