Re: an interoperable object (fallback and context menus)

I would encourage you to file WebKit bugs at <http://bugs.webkit.org>  
or QuickTime bugs at <http://bugreport.apple.com> for any behavior you  
feel is a bug, or to comment in existing bugs.

I think your example does indeed show bugs, but I believe they are  
different from what you may think and don't involve QuickTime:

1) <object data="objectImage">
   --> In this case WebKit treats the <object> as a frame because it  
can't determine content type before loading. This is a WebKit bug.

https://bugs.webkit.org/show_bug.cgi?id=5793

2) <object type="image/png" data="objectImage">
   --> In this case, WebKit treats the <object> as an image (natively  
not via QuickTime) but our code for this does not offer context menus  
or the ability to drag the image, as it would for <img>. This is  
another WebKit bug.

I don't believe there is a bug on this yet. I encourage you to file  
one. There is the related bug <https://bugs.webkit.org/show_bug.cgi?id=16763 
 > about lack of context menus for fallback content, but I believe  
that is a separate bug.

3) <object data="objectImage.png">
   --> In this case, WebKit guesses based on extension that the  
<object> refers to a PNG image (an evil hack that often works). THe  
lack of context menus and draggability is due to issue 2.

4) <object type="image/png" data="objectImage.png">
   --> Same as issue 2.

This is my diagnosis based on testing with the Safari 4 beta and a  
recent WebKit nightly on Mac OS X 10.5.6 "Leopard".

Here is some other <object> bugs that are probably of concern to those  
who'd like to use it for images:

https://bugs.webkit.org/show_bug.cgi?id=10992
https://bugs.webkit.org/show_bug.cgi?id=5793

If you have cases where QuickTime is used to display an image instead  
of native rendering, that would be a bug as well.

Regards,
Maciej


On Mar 18, 2009, at 1:15 PM, Leif Halvard Silli wrote:

>
>
> Message summary:
>
> 1. Webkit should fix how it handles OBJECT images in the
>   single case when it *does* handle them on its own.
> 2. For the other cases, if Webkit can't ask QuickTime to
>   a. ensure that users get contextual menus for OBJECT images
>   b. and that users get fallback if the data URI fails,
>   then Webkit ought to start handle such images on its own -
>   like the other browsers seem to do.
> 3. If QuickTime *is* asked to improve, they should be told to:
>   a. offer same/similar *image* context menus as Webkit;
>   b. offer the HTML fallback if image URL is wrong (instead
>      of that lousy questionmark that one currently gets).
> 4. Webkit may have a cool URI problem for images in general.
>
> Video and other plug-ins are one thing - users are pretty used to  
> differing interfaces for vidoes. But everything that <img> can  
> handle, <object> should treat the same. /That/ was the original  
> focus of this thread, including the original test page [1] - and  
> also of the new Webkit biased test page [2]. (Chris should also look  
> at that page despite its Webkit bias.)
>
> (A) To get Webkit to deliver OBJECT images with context menus and  
> fallback (the new test page - image 1 and 6 demonstrate the fallback  
> issue [2]), authors must currently ensure that Webkit *doesn't* use  
> the plug-in to load the image.  Possibly the fallback problem also  
> affects Safari + VoiceOver?!
>
> (B) To achieve the above, one must use <object data="Cool-URI">.  
> That is: no  file suffix and also no (or possibly an unknown) MIME  
> must be set by @type.
>
> (C) In addition - to make it look nice - one must also set the  
> object dimensions - which must be specified to exactly match the  
> intrinsic size of the image. Or else, Webkit makes the image look  
> like in IE6 and IE7 (or IE8 in quirks mode).
>
> (E) The fallback problems when QuickTime takes care of the display  
> really hints that there is something lacking w.r.t. to the  
> undersanding/specification of how and when fallback is delivered -   
> especially w.r.t. the interaction of plug-in and browser.
>
> (E) There seems also to be a problem with the handling of cool URIs  
> for images in general - disregarding whether one uses <img> or  
> <object> - which makes images with a cool URI load after the images  
> with a direct URI. I do not seem to see this in Opera, Firefox. And  
> also I do not see it in Safari 3/current iCab when QuickTime loads  
> the images. (Safari 4 seem to handle the cool uri aspect better -  
> but I don't know if this is due to a general speed bump or becuase I  
> run it on a faster test computer.)
>
> [1] http://www.malform.no/html5/object
> [2] http://www.malform.no/html5/object+webkit
> -- 
> leif halvard silli

Received on Wednesday, 18 March 2009 20:47:39 UTC