|
What has been fixed in NetObjects Fusion MX.
APPLICATION
NetObjects Fusion wouldn’t open your site to the last page that was viewed in Page Design view.
NetObjects Fusion wouldn’t open your site to the last page that was viewed in Page Design view. This has been fixed in MX.
NetObjects Fusion wouldn’t detect Netscape 6 was installed.
NetObjects Fusion wouldn’t detect that Netscape 6 is installed on your machine and offer it as a choice in the Preview settings. This has been fixed in MX.
Links in Help menu wouldn’t open the Web page.
Links (NetObjects Web Site, eFuse, etc.) in Help menu wouldn’t open the Web page. The browser window would say page not found. This has been fixed in MX.
The component toolbars wouldn’t stay docked.
The component toolbars wouldn’t stay docked or in the same position when you close your site file. This has been fixed in MX.
CRASHERS
Pasted text that originated from a paragraph containing an image background would cause the program to crash.
Copying and pasting text from a paragraph that contained an image as a background would cause NetObjects Fusion to crash. This has been fixed in MX.
Adding custom text style to the body would cause the SiteStyle to become unstable.
When adding custom text style to the body, the edited Style would become unusable until the offending CSS is edited out. Any site based on that Style would be unusable. This has been fixed in MX.
Size Objects feature caused the site to become unstable or the program to stop running.
If you tried to resize two objects using the Size Objects feature in the Multi-Objects Properties palette, this would cause your site to become unstable or would cause the program to crash. This has been fixed in MX.
DynaButtons when placed when Style background set to None caused the program to crash.
If the Style background is set to None for a SiteStyle and then you go to Page view and place a DynaButton on the page, the computer would crash. This has been fixed in MX.
ACTIONS
Actions in your site file would cause the site file to increase in size.
When using actions in your site file, the site file would increase in size every time you opened and closed the site file. This has been fixed in MX
COMPONENTS
Publish Components invoked when going to HTML Source view.
If you were using the DDC or the Cold Fusion component in your site file, when you go to the HTML Source view the Publish Components would be invoked. This has been fixed in MX.
DATA OBJECTS
Having a form in your site file would cause the images in stacked pages to not be displayed.
If you have a form on a page that is published before stacked pages with image data fields, then the image data fields are broken in the published site. This has been fixed in MX.
IMAGES
Couldn’t set a GIF image in a text box to “Transparency.”
If you placed a GIF image in a text box, you couldn’t select the Transparency setting in the properties palette. This has been fixed in MX.
PUBLISH
“Selected Page only” not defaulting to page selected in Site view.
When publishing Selected Page only, in the Publish Site dialog, NetObjects Fusion would not default to the page that was selected in Site view. This has been fixed in MX.
TEXT and LINKS
Hover color not working on visited links.
If you would set the Hover color for a link and set a different color for the Visited link. When you published the page the Hover feature wouldn’t work on the Visited link. This has been fixed in MX.
Anchor lost after changing MasterBorder to AutoFrames.
If you created anchors on a page and had links to those anchors, then changed the page so that your MasterBorder had frames, you would lose the anchors. This has been fixed in MX.
Adding a hotspot to an image linked to a deleted anchor adds “>” and an alt tag.
If you added a hotspot to an image and linked to an anchor, then deleted that anchor, the published page would have an “>” and an alt tag for the delete anchor. This has been fixed in MX.
|
