Boyd Ferris's dashboard

The flash control is covering the Seadragon Ajax element, capturing the mouse input. Add z-index to your CSS to ensure that the Seadragon Ajax container is above your flash. Also, the bigger problem that you have with your site is that it does not render well in Firefox, which is probably caused by setting the bottom and top property with your #flash CSS. The top and bottom properties are mutually exclusive; you should use only the top and left property to set your flash control to the top-left corner with absolute positioning.

In summary: add z-index to alleviate mouse capture issues and remove the bottom and right property from #flash css.

By default, web servers do not recognize the .dzi extension, so in order to avoid having to manually register the dzi extension or to accommodate others who use a hosted web server, the xml extension is used.

As for your problem, you are running into a cross-site scripting security issue, which you can read about here: http://en.wikipedia.org/wiki/Cross_si.... In order to work around this issue, we have a service that allows you to conveniently embed Seadragon Ajax into a page, which is located at http://livelabs.com/seadragon-ajax/em.... The embed viewer safely works around the cross-site security issue and still exposes the Seadragon Ajax API.

That is certaiinly unexpected: the two browsers are the same version but works differently on your machine. This next suggestion may be a bit too techy, but if it is something that you can easily do, then it can provide an answer to the problem.

1. On your coworker's machine, get the source for the web page. (You can get the source by right-clicking on the web page and selecting "View source" from the context menu.)

2. Get the web page source from your machine.

3. Compare the files and look for anything different. A tool like WindDiff, located at http://keithdevens.com/files/windiff, will be very useful for the comparison.

4. Note any differences. If the files are exactly the same, then there is not much that can be done without personally spending a lot of time with your machine. Though, if the files are the same, then disable any third-party navigation toolbar, such as a Yahoo Toolbar or MSN Toolbar, and see if that fixes the problem.

Seadragon Ajax is not fully supported on IE 6 because it does not support some of the newer web standards, specificially the newer specifications in cascading style sheets. IE7+, Firefox 2+, and many other browsers do support these newer web standards.

While IE 6 is not fully supported, you should still be able to see the navigation buttons. Do you have a link to a web page that is exhibiting this problem?

Thanks for your input,

Boyd

Yes. The nav bar is a control that is created by the API, so you can just remove the control and then add the control back with the desired location. Here is a code snippet that moves the nav bar from the default bottom-right location to the opposite corner:

var navBarControl = seadragonControl.getNavControl();
seadragonControl.removeControl(navBarControl);

seadragonControl.addControl(navBarControl, Seadragon.ControlAnchor.TOP_LEFT);

Change the extension from dzi to xml. The hosting web server may not be able to pass files with a diz extension through, changing the file to an XML extension will solve this issue.

Thanks for the post. I did find the following issue with IE 8 Beta 2: after bringing up the Seadragon Ajax About dialog and then exiting this dialog, the image could be moved outside of the viewport boundaries. Is this the same issue that you came across?

This issue (as well as other issues with IE 8 Beta 2) are bugs that are in the beta release. These bugs have been corrected, and Seadragon Ajax does not exhibit the About dialog issue with the most recent build of IE 8, which is not available publicly. We test against IE 8, and Seadragon Ajax will fully work with the full product release of IE 8.