Bug 49015

Summary: handle plugins without mimetypes in fast/js/navigator-mimeTypes-length.html
Product: WebKit Reporter: Tony Chang <tony>
Component: New BugsAssignee: Tony Chang <tony>
Status: RESOLVED FIXED    
Severity: Normal CC: ap, commit-queue
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Other   
OS: OS X 10.5   
Attachments:
Description Flags
Patch none

Tony Chang
Reported 2010-11-04 12:08:32 PDT
handle plugins without mimetypes in fast/js/navigator-mimeTypes-length.html
Attachments
Patch (3.99 KB, patch)
2010-11-04 12:12 PDT, Tony Chang
no flags
Tony Chang
Comment 1 2010-11-04 12:12:01 PDT
Tony Chang
Comment 2 2010-11-04 12:13:24 PDT
This test was added in https://bugs.webkit.org/show_bug.cgi?id=10038. We used to work around this in the chromium test plugin by registering 2 mime types, but I'm trying to switch chromium to using the plugin in WebKitTools/DumpRenderTree/TestNetscapePlugIn.
WebKit Commit Bot
Comment 3 2010-11-04 14:36:11 PDT
Comment on attachment 72970 [details] Patch Clearing flags on attachment: 72970 Committed r71357: <http://trac.webkit.org/changeset/71357>
WebKit Commit Bot
Comment 4 2010-11-04 14:36:16 PDT
All reviewed patches have been landed. Closing bug.
Alexey Proskuryakov
Comment 5 2010-11-05 23:35:07 PDT
Why is this test even in fast/js? It's not a pure JavaScript test.
Tony Chang
Comment 6 2010-11-08 09:43:30 PST
(In reply to comment #5) > Why is this test even in fast/js? It's not a pure JavaScript test. I don't know, you put it there :) Do you want me to move it to LayoutTests/plugins?
Alexey Proskuryakov
Comment 7 2010-11-08 10:05:45 PST
> I don't know, you put it there :) D'oh! > Do you want me to move it to LayoutTests/plugins? That's probably where it needs to be, but it is not your duty, of course.
Tony Chang
Comment 8 2010-11-08 13:42:34 PST
(In reply to comment #7) > > Do you want me to move it to LayoutTests/plugins? > > That's probably where it needs to be, but it is not your duty, of course. Moved in http://trac.webkit.org/changeset/71567.
Note You need to log in before you can comment on or make changes to this bug.