Last Comment Bug 847600 - Remove SVGEvent
: Remove SVGEvent
Status: RESOLVED FIXED
: dev-doc-needed, site-compat
Product: Core
Classification: Components
Component: DOM: Events (show other bugs)
: unspecified
: x86_64 Linux
: -- normal (vote)
: mozilla22
Assigned To: Olli Pettay [:smaug]
:
Mentors:
Depends on:
Blocks: 776864
  Show dependency treegraph
 
Reported: 2013-03-04 13:44 PST by Olli Pettay [:smaug]
Modified: 2013-05-16 11:53 PDT (History)
6 users (show)
See Also:
Crash Signature:
(edit)
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---


Attachments
patch (15.48 KB, patch)
2013-03-09 12:58 PST, Olli Pettay [:smaug]
jwatt: review+
Details | Diff | Review
patch (15.77 KB, patch)
2013-03-11 11:59 PDT, Olli Pettay [:smaug]
no flags Details | Diff | Review

Description Olli Pettay [:smaug] 2013-03-04 13:44:57 PST

    
Comment 1 Olli Pettay [:smaug] 2013-03-05 06:43:53 PST
It is not clear to me why we need SVGEvent interface at all.
Could we remove it?
Comment 2 Olli Pettay [:smaug] 2013-03-09 09:08:37 PST
Ping.

I'd like to avoid implementing useless events in Webidl.
Comment 3 Jonathan Watt [:jwatt] 2013-03-09 09:46:52 PST
The SVGEvent interface exists in SVG 1.0:

  http://www.w3.org/TR/SVG10/idl.html
  http://www.w3.org/TR/SVG10/script.html

but no longer exists in SVG 1.1:

  http://www.w3.org/TR/SVG11/idl.html
  http://www.w3.org/TR/SVG11/script.html

Seems like it can just go away. (Note the message types SVGLoad, SVGUnload, SVGAbort, SVGError, SVGResize and SVGScroll still exist, but we don't need the SVGEvent interface for them.)
Comment 4 Olli Pettay [:smaug] 2013-03-09 09:48:05 PST
Ok, thanks!
Comment 5 Olli Pettay [:smaug] 2013-03-09 12:58:26 PST
Created attachment 723111 [details] [diff] [review]
patch
Comment 6 Olli Pettay [:smaug] 2013-03-09 13:15:34 PST
https://tbpl.mozilla.org/?tree=Try&rev=84eab1736339
Comment 8 Ryan VanderMeulen [:RyanVM] 2013-03-12 12:59:01 PDT
https://hg.mozilla.org/mozilla-central/rev/d8648c78e3ad
Comment 9 Kohei Yoshino [:kohei] 2013-03-29 10:17:36 PDT
I've added this bug to the compatibility doc. Please correct the info if wrong.
https://developer.mozilla.org/en-US/docs/Site_Compatibility_for_Firefox_22

Note You need to log in before you can comment on or make changes to this bug.