Posts in Category "Announcements"

BrowserLab is shutting down on March 13, 2013

Dear BrowserLab customers,

When we originally launched BrowserLab as a free service back in 2009, our customers were struggling with testing their web content across desktop browsers and platforms. Since then with the growth of the importance of mobile devices and tablets, the landscape has changed dramatically. Because of this shift, we have seen the usage of BrowserLab drop over the past year while at the same time our engineering team has been focusing on solving this new challenge with new solutions. Due to this, we will be shutting down the Adobe BrowserLab Service effective immediately.

If you need to test across multiple desktop browsers, we recommend that you check out BrowserStack and Sauce Labs as two viable alternatives to BrowserLab. Our friends at Sauce Labs are welcoming BrowserLab users with a special offer:

  • 10 hours (600 minutes) of free manual testing time (with no expiration) for up to two concurrent open browsers
  • Once you’ve used those 600 minutes, your account will revert to a free account which includes 30 minutes per month of free manual browser testing
  • This limited time offer will remain valid for 30 days from the date of this blog post

If you are working on mobile web projects, check out Adobe Edge Inspect. It is designed to work on your computer to remotely control actual devices and will allow you to debug web pages directly on a mobile device or phone.

We’d like to thank all of our customers over the years for using and providing input for the Adobe BrowserLab Service.

Best Regards,
Bruce Bowman
Sr. Product Manager, Edge Tools & Services and the Adobe BrowserLab Team

BrowserLab update removes IE7

Internet Explorer 7 has been retired from BrowserLab

Today we have pushed a minor new version of BrowserLab that no longer contains Internet Explorer 7. If you still need to test for IE7 in BrowserLab, you can do this using IE8 and a by adding bit of code to your page(s). To learn more about IE8’s Compatibility Mode, you can read about it in these Microsoft Blogs:

Introducing Compatibility View
Understanding Compatibility Modes in Internet Explorer 8

Remember to remove that code once your testing is complete, unless you want your IE8 visitors to see your page as they would in IE7.

Bruce Bowman
Adobe BrowserLab product manager
twitter: @brucebowman

Adieu, au revoir, ciao, and adios to IE6

We’re (finally) removing Internet Explorer 6 from BrowserLab. Fortunately, we don’t need to include it in the set of browsers any more due to its final decline of usage. We’ve all been waiting for this day.

I wish I could say that we’re removing IE6 exclusively due to its utter and complete lack of relevance. While that’s mostly true, the fact of the matter is that we have an issue with continuing to support IE6, that in combination with its decline of use, made it an easy decision to terminate it. And, I must admit, it feels pretty good to have the last word in this long, painful, protracted battle.

So, IE6, I say to you – You’re out of my life for good. Adieu, au revoir, ciao, adios, sayonara! Good riddance. I will not miss you.

Bruce Bowman
Adobe BrowserLab product manager
twitter: @brucebowman

BrowserLab adds Chrome 18 support

BrowserLab v1.6.6 is now live, and contains the following changes:

  • Chrome 18 support (Windows)
  • New login screen

If you have any problems logging in to BrowserLab, please clear your cache and restart your browser, then try again. We made some significant changes to the login mechanism, so this step may be necessary.

We will update BrowserLab again soon to add the latest Flash Player, and a newer version of Firefox.

Bruce Bowman
Adobe BrowserLab product manager
twitter: @brucebowman

BrowserLab Pricing and Roadmap Announcements

Today we’re pleased to announce that BrowserLab will continue to be free/complimentary, and will not become a paid service in April 2012 as we had previously communicated.

BrowserLab is no longer part of Adobe CS Live. BrowserLab will continue to be available as you use it today, and we do not expect any interruptions in service. We will continue to make updates to BrowserLab, to add new versions of our Browsers, and to keep the service running smoothly and securely.

You may have noticed that the team has been pretty quiet lately, and updates to the BrowserLab service have slowed down over the last few months. This is because the BrowserLab team has been busy working on a new project (UPDATE: Read about Adobe Shadow on the Shadow Team Blog), which will be a nice companion tool to BrowserLab. We think most BrowserLab users will be very interested in the new product, and we’re excited to share it with you. We’re going to unveil it soon, and the first public showing will be on March 12, 2012 at the SxSW Interactive conference in Austin, TX.

If you’re going to SxSW this year, or interested in knowing what we’re doing there , please follow us on twitter @AdobeSxSW.
Bruce Bowman
Adobe BrowserLab product manager
twitter: @brucebowman

BrowserLab 1.6.4 with new Chrome and Firefox browsers is now live

Today we have released a new version of BrowserLab for you, v1211P.312309, with updated browsers, security patches and some minor improvements:

  • Chrome 14 was added (Windows), and Chrome 11 was removed
  • Firefox 7 was added (Mac OS X and Windows), and Firefox 4 was removed
  • Safari was updated to 5.1 (Mac OS X)
  • Flash Player was updated to (Mac OS X and Windows)

We will include Flash Player 11 in our next update.

Bruce Bowman
Adobe BrowserLab product manager
twitter: @brucebowman

BrowserLab 1.6.3 with new Mac OS X browsers is now live

Today we have released a new version of BrowserLab for you, v1168P.306117, which has some nice improvements:

  • Chrome 13 beta was updated to the final release (Windows)
  • Firefox 4 was added (Mac OS X)
  • Firefox 5 was added (Mac OS X)
  • Flash Player was updated to v10.3 (Mac OS X)

We also updated our BrowserLab for Firebug Add-on for Firebug 1.8. You can find it on the Mozilla Add-ons page, or if you already have it installed, it will be updated when you update your Add-ons.

Finally, we have removed support for some older browsers now that they’ve significantly declined in usage. Safari 4 (Mac OS X), and Firefox 3 and 3.6 (Mac OS X and Windows) have been removed.

Bruce Bowman
Adobe BrowserLab product manager
twitter: @brucebowman

BrowserLab v1.6.2 with Firefox 5 and Chrome 13 support is now live

This afternoon, we released BrowserLab v1.6.2 which includes the following changes:

  • Chrome 13 (Windows) support has been added
  • Firefox 5 (Windows) support has been added
  • A fix that improves BrowserLab’s support for sites built with the SilverStripe CMS
  • Additional bug fixes and improvements

Someday in the not too distant future, we’re going to remove Firefox 3.0 and 3.6 from BrowserLab. If you’re wondering why we would remove support for older browsers, it is to keep BrowserLab lean and mean, and keep our backend costs in check. We can’t keep older browsers around forever, and we’ve seen significant drop-off in market share for these older versions. If you have objections to this, please let us know why. You can let us know how you feel by posting here in the Comments, or on our BrowserLab User Forums.

Bruce Bowman
Adobe BrowserLab product manager
twitter: @brucebowman

BrowserLab 1.6.1 is live: now with Chrome 11

Today we rolled out BrowserLab v1.6.1 which includes some nice changes:

  • Chrome 11 (Windows) was added, and Chrome 9 was removed
  • We’ve added an in-client poll/survey that asks you 2 simple questions. Please take the survey as it will only take you a minute, and it will help us measure and improve the service
  • We fixed several bugs, including some fixes for isses we had loading pages that use Modernizr
  • We increased the maximum range value for our Delay feature from 10 to 20 seconds

We recently spoke to some BrowserLab users that were not aware of the Delay feature in BrowserLab. If you’ve never tried it, the Delay feature allows you to specify how long BrowserLab should wait after loading your page before the screenshots are taken. This is useful when you have dynamic content such as movies, animations, etc that needs time to load or play before you want your screenshot to be taken. Generally, you’ll want to leave the Delay set to 0 unless your content is not loading, or it will needlessly increase the time it takes to return your screenshots.

Bruce Bowman
Adobe BrowserLab product manager
twitter: @brucebowman

BrowserLab v1.6 is now live

Coinciding with the release of Creative Suite 5.5, we’re now live with BrowserLab v1.6. This release adds some nice new features, such as Follow Links, URL History, new Italian and Spanish language support, as well as workflow improvements with BrowserLab for Dreamweaver. BrowserLab can be used in the following ways, one of which is sure to fit into your workflow:

  • BrowserLab Client: Access BrowserLab in your web browser, enter the URL, and do your cross-browser testing.
  • BrowserLab for Firebug: This Firefox extension allows you to test local content, that might have been changed using Firebug. It also enables you to test sites that are behind HTTP Authentication – just open your site in Firefox, log-in, then use BrowserLab for Firebug to Preview Local Source. We have a short AdobeTV movie showing this workflow
  • BrowserLab for Dreamweaver: Using Adobe Dreamweaver CS 5 or CS 5.5, you can send your current document to BrowserLab. This works with files that are on your Remote or Local servers. Using Dreamweaver’s powerful Freeze JavaScript feature, you can browse your site in the built-in WebKit browser, get it into a state, freeze, then send that to BrowserLab. BrowserLab will render your page, in that frozen state across all of the browsers in your Browser Set. Another AdobeTV movie shows the BrowserLab for Dreamweaver workflow.

On behalf of the whole BrowserLab Team, I’m happy to announce the immediate availability of BrowserLab v1.6. We hope you enjoy using it as much as we enjoy making it!

Bruce Bowman
Adobe BrowserLab product manager
twitter: @brucebowman