Adobe BrowserLab known issues

Issue: BrowserLab doesn't load in your web browser, or features in BrowserLab function inconsistently or not at all.

Solution:

Make sure that you're using a browser supported by BrowserLab. For a list of supported browsers, see the CS Live system requirements: http://www.adobe.com/products/creativesuite/cslive/tech-specs.html



If your browser is supported and you are still experiencing one or more issues, report the issue on the BrowserLab forum: http://forums.adobe.com/community/cslive/browserlab

Issue: When you test a page whose layout is more than 4096 pixels on any side, the screenshot in BrowserLab is cropped at 4096 pixels.

Solution: None. This behavior is as designed.

Issue: When you test a page that contains a "floating" footer, the footer is in an unexpected location such as in the middle of the page. (A floating footer is one that is designed to float at the bottom of the browser while a user scrolls up or down.) (2360620, 2843440)

This issue most often occurs when you test as Internet Explorer 6 or as Firefox.

Solution: There is currently no workaround for this issue.

Issue: When you try to test a page located on a server that is not publicly accessible, BrowserLab cannot display a screenshot. (For example, a server that isn't publicly available include servers that are on your own computer or on a company intranet.)

Solution: To preview a page located on a server that is not publicly accessible, use the Local/Network option in Dreamweaver. Or use the Preview Local Source in BrowserLab for Firebug.

Issue: When you preview dynamic sites using the Preview Local/Network option in Dreamweaver, the source file is sent to BrowserLab is raw code. Screenshots are not rendered.

Solution: When you preview dynamic sites (that is, PHP pages) using the BrowserLab panel Preview Local/Network option, ensure that you are in “Live View” mode. Alternatively, you can also use the Remote Server site setup option. Then in the BrowserLab panel, choose Preview Server instead if your Remote server is publicly accessible or visible.

Issue: When you try to test a page or application secured by HTTP authentication, BrowserLab cannot display a screenshot.

Solution: Use the Preview Local/Network option in Dreamweaver or the Preview Local Source in BrowserLab for Firebug to test the content.

Issue: When you test a page on a site that uses SSL, BrowserLab displays inconsistent screenshots or doesn't display the page.

Solution: To test pages via HTTPS in BrowserLab, make sure that the site has a valid SSL certificate.

Issue: When you test a page that redirects to another page, BrowserLab displays screenshots unpredictably.

Solution: For predictable results, test the destination page instead of the redirection page.

Issue: When you try to test your page in BrowserLab using Dreamweaver CS4 or CS5, no screenshots are loaded in BrowserLab.

Solution:

Dreamweaver CS4: BrowserLab integration with Dreamweaver CS4 is no longer supported. Upgrade to Dreamweaver CS5.5 to continue using BrowserLab as an integrated service. Alternatively, use BrowserLab for Firebug, or test your content directly in BrowserLab using your web browser of choice.



Dreamweaver CS5: Install the 11.0.4 update for Dreamweaver CS5 to enable BrowserLab integration. To install the update automatically, choose Help > Updates in Dreamweaver. You can also download the update from the Adobe website:  http://www.adobe.com/support/dreamweaver/downloads_updaters.html

Issue: After you update Flash Player on a computer running a 64-bit edition of Windows Vista, Dreamweaver integration features don't function as expected.

Solution: Restart your computer before using BrowserLab with Dreamweaver.

Issue: When you test a page in BrowserLab from Dreamweaver on Windows, your web browser sometimes doesn't appear in front of other open windows.

Solution: Bring your browser window to the front or restore it from a minimized state. For example, click the application in the Windows taskbar or use Alt+Tab to bring it forward or restore it from a minimized state.

Issue: When you test a dynamic page (for example, a PHP page) using the Preview Local/Network option, BrowserLab displays a screenshot of raw code. Or, it cannot display a screenshot.

Solution: Turn on Live View. It's necessary to be in Live View to test dynamic pages in Dreamweaver or BrowserLab. Alternatively, if your server is publicly accessible, use Preview Server in Dreamweaver to test the page from the Remote Server.

Issue: Real-time updates to your code in Dreamweaver aren't rendered in BrowserLab.

Solution: Press F5 or Refresh Design View in Dreamweaver before selecting Preview in BrowserLab.

Issue: When you test a page that includes elements drawn dynamically after the page loads in the Dreamweaver Live View, BrowserLab displays an inaccurate screenshot.

Solution: Turn off Freeze JavaScript in Dreamweaver. To do so, press F6 or select View > Live View Options and deselect Freeze JavaScript.

Issue: When you test a page located on a local Testing Server in the Dreamweaver Live View, BrowserLab cannot display a screenshot.

Solution: Use the Preview Local/Network option in Dreamweaver to preview pages located on localhost or a private network.

Issue: When you test your page in BrowserLab using the Preview Local/Network option in Dreamweaver, BrowserLab cannot display a screenshot.

Solution: Verify that the paths in your Dreamweaver Site Settings are correct and that each letter matches case with the local file system.

Issue: When you Preview Local Source using Firefox 3.5 or later, the screenshots shown in BrowserLab are incorrect.



This issue is known to occur if Firefox has restored a previous browsing session. This issue can occur in the following situations:

• if you have the Show My Windows And Tabs setting enabled in Firefox
• if you use a session manager add-on to automatically restore tabs/windows each time you open Firefox
• if Firefox restored a previously crashed session.

 

Solution: Clear the browser cache and restart Firefox. To avoid future issues with the Show My Windows And Tabs setting, consider disabling it. If you use a session manager, then exclude BrowserLab from automatic session restoration to avoid issues.

Issue: Real-time updates to your code via the BrowserLab for Firebug Add-on isn't always rendered in BrowserLab.

Solution: Make sure that the expected updates are visible in your local instance of Firefox before selecting Preview Local Source in the BrowserLab for Firebug add-on.