Mailing Lists: Apple Mailing Lists

Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Safari applet problem with object tag



Thanks for the replies to my query, and apologies for the delay in response - time zones and work crisis. Just a couple of brief points.

GG wrote:

The HTML 4 spec, which I only glanced at:
  <http://www.w3.org/TR/html4/struct/objects.html#h-13.3.2>

says the PARAM tag is an empty tag, so try this representation:
  <PARAM NAME="progressbar" VALUE="true" />

Note the / before the >. I'm just wildly guessing though.

An empty tag in HTML does *not* need the />, which is only required to close the tag in XHTML. The page is marked up as HTML 4.01 strict and validates against the W3C validator. Safari doesn't require any other empty tags to be closed.


damieng wrote:

This lets us know what the standard is. Unfortunately, it doesn't work
with Safari. It works with
any other web browser, though (except Shiira).
My conclusion is that Safari does not support HTML4, and never has.

Let's not be too hard on Safari. There are other aspects of the HTML 4 spec that other browsers don't support - it's just not that simple. I don't find the HTML Object spec easy to understand either. Furthermore Safari is the only browser that passes the web standards Acid2 test <http://www.webstandards.org/act/acid2/>. I know that cross platform/browser applet markup has been a mess (I've wasted time on Sun's site too), but with browsers converging more and more on standards compliance it would seem a resolution may soon be possible and it would seem worthwhile helping Safari to get this right (if indeed it has it wrong).


GG wrote:

Deprecated doesn't mean obsolete.  One could use the deprecated <APPLET>
tag to embed applets:
  <http://www.w3.org/TR/html4/conform.html#deprecated>
   "User agents should continue to support deprecated elements for
    reasons of backward compatibility."

One would then have to reference the Transitional DTD, not the Strict one.

That's true at the moment. I would say there is a 50:50 chance that IE7 will drop support for the deprecated <applet> tag. After all, isn't that what's supposed to happen eventually?


Morten reckons Safari has a problem with 'codebase' and the object tag, and will file a bug. He also suggests a workaround by putting the jar file at the same level as the web page, which I will try when I get into work. Many thanks.

David
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden

This email sent to email@hidden


Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.