| Summary: | new HTML wizard does not handle .HTML extension (capitalized) | ||
|---|---|---|---|
| Product: | [WebTools] WTP Source Editing | Reporter: | Ying Chen <ying1> |
| Component: | wst.html | Assignee: | Amy Wu <for.work.things> |
| Status: | CLOSED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | Keywords: | Documentation |
| Version: | unspecified | ||
| Target Milestone: | 1.5 M5 | ||
| Hardware: | PC | ||
| OS: | Windows XP | ||
| Whiteboard: | |||
|
Description
Ying Chen
Amy ... mind if I "double up" ... as you look to fix this (please check if there's a base bug in contentType support) ... Also please consider 1. not requiring an extension at all (and assume "first"?) for file preferred file type, 2. if a non-qualifying filetype is used, detect this and offer a user choice for adding to contentType definition? As always, your recommendation is desired. All our wizards (xml, html, jsp, js, css, dtd) were fixed so that the extension check/validation is case insensitive. I also took David's suggestion #1 into consideration. A new preference was added to all the "xx Files" preference pages, "Add this suffix (if not specified):" This allows users to specify their own default extension, so if they do not specify one in the new file wizards, the default one will be used. Added Documentation keyword to flag UI changes made (explained in comment #2) verified the fix... closing |