| Summary: | Remove initWebKitTransitionEvent method | ||||||
|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Dominic Cooney <dominicc> | ||||
| Component: | DOM | Assignee: | Dominic Cooney <dominicc> | ||||
| Status: | RESOLVED FIXED | ||||||
| Severity: | Normal | CC: | abarth, ojan, webkit.review.bot | ||||
| Priority: | P2 | ||||||
| Version: | 528+ (Nightly build) | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Bug Depends on: | |||||||
| Bug Blocks: | 68791 | ||||||
| Attachments: |
|
||||||
|
Description
Dominic Cooney
2011-11-07 09:30:44 PST
Created attachment 113884 [details]
Patch
Comment on attachment 113884 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=113884&action=review > Source/WebCore/ChangeLog:9 > + Now that WebKitTransitionEvent has a constructor, we don't need > + this method. Please include the information that init*Event methods have been removed from the spec. Comment on attachment 113884 [details] Patch Removing this from the commit queue for now. I filed <https://www.w3.org/Bugs/Public/show_bug.cgi?id=15339> to remove the initTransitionEvent from the spec. I don't think you need to wait for the spec to be updated here. The platform as a whole is clearly moving in this direction, so it seems very unlikely to me that this spec won't be updated eventually to match. The longer this stays in trunk, the more likely we'll get stuck unable to remove it due to compatibility concerns. Filing the spec bug is important of course. Comment on attachment 113884 [details]
Patch
Agreed. This is definitely the direction the platform is headed.
|