And another load: - When inserting text in the middle of a line, garbage pixels interfere with the newly types text. It looks like the area where the new characters are placed is never properly cleared. - Selecting and then deselecting often leaves the lowest line of pixels from the selected text, making the text appear to be underlined. - Many of the different list types all result in an <OL> (ordered list) tag, also ones that shouldn't. - The <BLOCKQUOTE> tag is rendered as a lot of empty lines in the WYSIWIG window, possibly one line per word. After a few load/save attempts and sometimes even after clicking the 'refresh source' button a couple of times, the tag is removed all of a sudden. - When typing in the WYSIWIG window and nearing the bottom edge of the window, new text typed will happen off-screen. When pressing <Enter> the proportional slider will be resized, but the window does not scroll down to see the new line and cursor. This means you have to move the window everytime you start typing on the next line. - Many of the HTML text tags (citation, teletype, etc.) are modified or removed by MetalWeb. The application should never do something with tags it doesn't recognize, they should simply be ignored. - Using tables is impossible from the WYSIWIG window. Almost all types of table formatting (percentage width, etc.) are ignored or changed from the values entered, and editing inside a cell almost always produces unexpected results, with cells disappearing from the WYSIWIG view, formatting being changed, and so on. - When deleting selected text, the character under the cursor is deleted in the source window, but not in the WYSIWIG window. Quite a few of these things seem to relate to MetalWeb modifying the HTML code without it being told to do so. It should never do that. It does not only change or remove tags, but also make structural changes. Also, HTML tag items that are set to default when not defined (like frame borders, for example) should not have 0 as default setting, but also allow the real default setting, which is represented by not putting the tag in the HTML code. Any page created with MetalWeb will have no frameborders and the MetalWeb settings for background, text, link and visited link. When these tags are removed from the HTML file manually, they will be reinserted by MetalWeb. That is bad. And yes, I am also looking forward to the next version. I only hope that as a registered user of the current version, I will not be forced to pay to get the functionality that I already paid for and did not get with this version. I am a programmer myself and like the concept of MetalWeb, but in it's current state I would not have released it to the public. This is definitely a product that is still in it's alpha testing phase and I do not believe that the pages seen in the MetalWeb ad are made by MetalWeb. Currently, that is simply not possible. Wouter Lamee.
