Bug 40492 – onpaste

• Status: RESOLVED
• Resolution: INVALID
• Component: SVG

[jay]

is there any inherent reason why the safari javascript "support to let you handle cut, copy, and paste operations of your HTML content" 
should not be available within SVG?

---

http://developer.apple.com/mac/library/documentation/AppleApplications/Conceptual/SafariJSProgTopics/Tasks/CopyAndPaste.html

support for text editing in SVG, together with xForms is currently limited, or non-existent.

implementing SVG1.2 editable text fields might help somewhat, but this bug may still remain

http://www.honte.eu/register.svg currently runs from my laptop, has no fixed ipaddress and may well move to http://www.honte.eu once stable.
the text fields are edited using script and the DOM, to partially emulate an html form


a related issue is raising a virtual keypad, ie for Android, iPad etc within SVG

[jay]

Created attachment 58499 [details]
html testcase

[Alexey Proskuryakov]

I don't understand this bug report. What is expected behavior on this test case? And why is it HTML if you are talking about SVG?

[jay]

#2 Alexey, the expected behaviour is that plain text content of clipboard is pasted into textbox, onpaste  event.
 paste any text into textbox, note predicate "clipboard: " is added

[jay]

Created attachment 58584 [details]
html testcase, paste clipboard text into textbox

[jay]

Created attachment 58586 [details]
SVG pseudo-code?

[jay]

apologies, this example is my 'best effort' at how I imagine this might work in SVG. the updated HTML example should now demonstrate clearly the intention, ie to provide a means to paste the plain/text clipboard contents into  an SVG document.

[Ryosuke Niwa]

I don't understand the bug either.  Is this bug about firing copy/paste events in SVG documents?

[jay]

#7

whilst not advocating Amaya, it does provide some possibilities to copy and paste between SVG documents.

basic text copying is part of the SVG1.1 spec iirc, else 1.2
in either case, the user expectation is that they can copy/paste text at a minimum,
SVG isn't bitmaps...

[Ryosuke Niwa]

(In reply to comment #8)
> whilst not advocating Amaya, it does provide some possibilities to copy and paste between SVG documents.
> 
> basic text copying is part of the SVG1.1 spec iirc, else 1.2
> in either case, the user expectation is that they can copy/paste text at a minimum,
> SVG isn't bitmaps...

Are you saying that you can't copy text in SVG?

[Ryosuke Niwa]

Nobody but the bug reporter understands what this bug report is about.

[jay]

#10 Niwa did you copy and paste as per comment #3?

please read this is simple and easy to understand for anyone.

please dont just add bug spam

[jay]

SVG text is in SVG attachment, copy it and paste into html textbox, in other attachment

[Ryosuke Niwa]

(In reply to comment #11)
> #10 Niwa did you copy and paste as per comment #3?

The expected behavior in comment #3 is exactly what happens when I try.

[jay]

Created attachment 98752 [details]
clip grab using: Version 5.0.5 (5533.21.1, r88541)

[jay]

as you can see in the clip image the word clipboard is duplicated...

[Ryosuke Niwa]

(In reply to comment #15)
> as you can see in the clip image the word clipboard is duplicated...

That's because you're appending "clipboard: " in attachment 58584 [details].

[Ryosuke Niwa]

It works as expected.

[jay]

it is not!

please do not make such assertions without checking first!

[Ryosuke Niwa]

(In reply to comment #18)
> it is not!
> 
> please do not make such assertions without checking first!

    function myPaste(event) {
     event.preventDefault();
event.currentTarget.value = "clipboard: " + event.clipboardData.getData("text/plain");
}

[jay]

Created attachment 98756 [details]
without script version...

[jay]

that is why it is marked pseudo, because the effect is as if the script was there, but it isnt needed...

my apologies if this is not as clear as it could be,

but there are some stubborn people in this world

[Alexey Proskuryakov]

Please provide an actual test case and clear steps to reproduce. A "pseudo" test that behaves correctly is not a starting point for investigation. There is no reason to keep a bug open if no one can understand it.

[jay]

moved to #63510