This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 9111 - Amaya doesn't handle applet tags properly
Summary: Amaya doesn't handle applet tags properly
Status: RESOLVED FIXED
Alias: None
Product: Amaya
Classification: Unclassified
Component: Misc (show other bugs)
Version: 11.3.1
Hardware: PC Windows NT
: P2 major
Target Milestone: ---
Assignee: Vatton
QA Contact: Vatton
URL: http://lists.w3.org/Archives/Public/w...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-21 23:56 UTC by Helder Magalh
Modified: 2010-02-23 15:56 UTC (History)
5 users (show)

See Also:


Attachments

Description Helder Magalh 2010-02-21 23:56:01 UTC
Amaya seems to be faulty at handling applet elements, either removing and/or changing their order within the document, which leads to breaking the whole document.


Steps to reproduce:
1. Create a new XHTML document;
2. Go to the source view and paste the following snippet into the "body" tag:

<applet height="100px" width="100px"><param name="foo" value="bar" />Fallback content</applet>
<p>Type something here</p>

3. Go to WYSIWYG view and type something into the paragraph that follows the applet tag;
4. Change to source view again (or just save the document).


Expected results:
Modifying any content within the page (step 3) would be harmless.


Actual results:
Modifying the paragraph that follows (step 3) and switching to source view (step 4) breaks the applet tag completely:

<param name="foo" value="bar" />
<p>Fallback content 
<p>Type something herex</p>

This kind of breaking affect the whole document also, which is serious.


Additional information:
The problem seems to be triggered by including the "param" element. A standalone "applet" element is left untouched.

The problem is seen in HTML documents as well, just use the HTML way of closing empty elements.

This was originally reported by Francesco [1], later confirmed/clarified by Chaals [2].

My environment is:
 * Amaya 11.3.1 (Dec 9 2009), VC9 flavor;
 * Windows Vista SP2.


Workarounds:
A potentially plausible workaround can be using other tags [3] to include Java applications: "object" (standard) or "embed" (supported in most browsers). A quick test performed with "object" elements shows that it doesn't seem to trigger the same behavior.


[1] http://lists.w3.org/Archives/Public/www-amaya/2010JanMar/0056.html
[2] http://lists.w3.org/Archives/Public/www-amaya/2010JanMar/0092.html
[3] http://java.sun.com/j2se/1.5.0/docs/guide/plugin/developer_guide/using_tags.html
Comment 1 Vincent Quint 2010-02-23 15:56:34 UTC
There are two different cases here :

1 - If the doocument uses the XHTML 1.0 Strict DTD, the <applet> element is simply removed (but its content is preserved) by Amaya: <applet> is not valid for this DTD. The red button in the lower right corner is lit. If you click it, you get an error message explaining the problem.

2 - If the document does not use this DTD (it uses for instance HTML 4.01 or XHTML 1.0 Transitional), then the <applet> element is allowed. But there was a bug in Amaya: the <param> elements included in an <applet> element were moved by the parser outside of the <applet>.
This bug is fixed: the <param> elements stay now within the <applet>.

Vincent.