| Summary: | HTML editor emits wrong warnings on <applet> tag's code parameters | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [WebTools] WTP Source Editing | Reporter: | Michael Moser <mmo> | ||||
| Component: | wst.html | Assignee: | wst.html <wst.html-inbox> | ||||
| Status: | RESOLVED NOT_ECLIPSE | QA Contact: | Nick Sandonato <nsand.dev> | ||||
| Severity: | minor | ||||||
| Priority: | P3 | CC: | thatnitind | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 7 | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
Created attachment 182195 [details]
Zipped eclipse project containing all files mentioned in the description.
Michael, can you list the messages themselves directly as well? That will make it easier to understand what to look for. We do not do any validation of the code attribute for the applet tag. This is likely an adopter product creating these annotations. |
The HTML editor obviously has some problems with the <applet ...>-tag's code="..." parameter. It puts "wiggles" under valid values (and emits warnings where it *should not*) and does *not* put wiggles (and does not emit warnings) for values where it *should*. To give a reproducible example I have created a test project, where an HTLML file "test.html" tries to reference an applet "test.Test" that is available as plain class file (WebContent/WEB-INF/classes/test/Test.class) and packed into a .jar file (WebContent/WEB-INF/lib/test.jar): <WebContent> WEB-INF classes test Test.class lib test.jar test.html Note: project setup and directory names are the defaults chosen by the misc. project and file creation wizards. The test.html files contains different variants of the code parameter. The actually *working* variants are 3, 4, 21, and 22, but the editor accepts the variants 5, 7, 14, 21, and 22, and emits warnings for all others, which means - except for the last two - the warnings *do not reflect* whether the parameter value is correct or not. To see the working variants, open the test.html file in your Java-enabled Browser. The working variants emit "Hello <nr>", all others hang for a while and/or yield exceptions. Michael