© Copyright International Business Machines Corporation 2006. All rights reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
Page Designer does not support non visual type CSS properties, for example speak.
Page Designer does not support the following visual type CSS properties:
border-collapse,border-spacing,caption-side,clip,content,counter-increment,counter-reset,cursor,empty-cells,font-variant,letter-spacing,max-height,max-width,min-height,min-width,orphans,outline-color,outline-style,outline-width,outline,overflow,page-break-after,page-break-before,page-break-inside,quotes,table-layout,visibility,widows and word-spacing.Page Designer does not fully support the following visual type CSS properties:
- Negative values of margin, margin-top, margin-bottom, margin-left and margin-right are not supported.
- Relative and fixed values of position are not supported.
- Values specified by percentage or length of vertical-align are not supported.
- Top and bottom values of vertical-align are not supported.
- Pre-wrap and pre-line values of white-space are not supported.
When a horizontal or vertical menu with the menu depth of greater than 3 is created, if the keepSelection property is true then hovering the mouse on the menu items should keep the sub-menu items expanded, but the third level menu items will not be kept expanded.
Drag and drop of a page from the WebContent folder of the Project Explorer view to the Navigation page of Web Site Navigation throws a null pointer exception.
If you select the Web Site Navigation project facet when you create a Web project, in the Select a page template for the Web site page in the wizard, you can select the Use a default Page Template for the Web site check box and select a sample template, but you can only select a design time template. You cannot select a dynamic page template.
If you make changes to the web.xml file, Web Site Navigation does not reflect your changes. For example, if the servlet mapping for a page in web.xml is changed, Web Site Navigation does not reflect this change on the Details page immediately or after you save the web.xml file.
Whenever a button name is translated from English to Russian (or some other language), the length of the translated string may be more than the length in the English string. If the button size remains the same then the name of the button appears truncated.
In English and other languages, a menu item will appear as Undo <Action>, for example Undo Adding Web Page but in Korean, the menu item should appear as <Action> Undo (for example Adding Web Page Undo). Currently these menu items display as Undo <Action>.
When you insert a navigation trail on one of the pages of the site, then changing the site does not reflect the changes in the Design page of Page Designer. You must refresh your screen, for example, by switching to the Preview page and then switching back to the Design page of Page Designer, to see the changes.
You may not be able to edit a file in Page Designer if the file is newly created by splitting a frame on the same Page Designer and if it is managed under SCM.
Workaround: Close the Page Designer and reopen the file.
When the caret appears outside of Free Layout table in the Design page of Page Designer, you cannot insert Free Layout table from the main menu.Workaround: Insert Free Layout table from the palette in this case.
When you use Page Designer along with resident screen reader software, the layout of Properties view may collapse.
Workaround: Do not use the Properties view with such software. Use All Attributes mode from "Show All Attributes" on local toolbar menu of the Properties view.
When you edit a Web diagram, context-sensitive help is available in a dynamic help view, but not in an infopop. To set a preference for displaying context-sensitive help in a dynamic help view: click Window > Preferences > Help, and then under Open window context help, click the in a dynamic help view radio button. If you click the in an infopop radio button, only general help is available when you edit a Web diagram.
Mixing HTML and JSP tags (including custom tags) may cause the HTML syntax validator to incorrectly report missing start and end tag errors. For example, in the following code:
<c:when test="${status.first}">
<div class="topNavRight"><ul>
</c:when>
...
<c:if test="${status.last}">
</ul></div>
</c:if>The <div> and <ul> start tags are within the <c:when> tags and the end </ul></div> tags are within the <c:if> tags. This is valid code; however, the HTML syntax validator reports that the </ul> and </div> tags are missing start tags.
Workaround #1: When possible, do not overlap the HTML and JSP tags. In the example above, the workaround would be to change the code to:
<div class="topNavRight"><ul>
<c:when test="${status.first}">
</c:when>
...
<c:if test="${status.last}">
</c:if>
</ul></div>Workaround #2: If overlapping is required, the workaround would be to disable HTML syntax validation. To disable HTML syntax validation in a project, invoke the Properties dialog for the project, select the Validation property page, check "Override validation preferences", clear "HTML Syntax Validator".