Meet an artistic member who has his own way of showing his thoughts and feelings.
His blog gives everyone a peek of life in his own country, India. From Mumbai life to a beatiful sunset he shares many great photograph
Fresh news about browsers. About most popular ones. Firefox, Inernet Explorer, Opera, Seamonkey, Webkit, Safari etc.
Meet an artistic member who has his own way of showing his thoughts and feelings.
His blog gives everyone a peek of life in his own country, India. From Mumbai life to a beatiful sunset he shares many great photograph
The giveaway has ended. Check out who won a free copy of Guy Kawasaki's "Reality Check"!
The following people have been drawn as winners of Guy Kawsaki's marketing bible, "Reality Check". Congratulations! The books will be sent out as soon as possible. :cool:
Soon we will update My Opera with many new features and improvements - as always.
Many of you use My Opera to share your photos. The current uploader has some limitations, but this is about to get fixed. With the upcoming release we will release a beta of our new photo uploader:
Preview of the new photo uploader
Other things you can look forward to is a br
2008 was a great year for Flock. We launched Flock 2.0, added integration with MySpace, Digg and WebMail, secured new funding and received numerous awards. And we reached an important milestone: Flock has been downloaded over 6 million times. While our technical accomplishments, partnerships and kudos from bloggers and the press mean a great deal to us, the most gratifying accomplishments of the year came from you, the people that use Flock every day.
Together you've made over 41 million log-ins across applications like Facebook, MySpace, YouTube, Flickr and Twitter. You've accessed nearly seven million photos and videos using the Media Bar and 25 million feeds via the Feeds Sidebar. You've stayed in touch with your friends by collectively loading more than 150 million people each and every month into the People Sidebar! And you've made almost one million blog posts using Flock. What you value inspires our direction and you've rewarded us by using Flock in record numbers. And by telling your friends about Flock. Your recommendations have been invaluable and, by our estimates, have contributed to more than 90% of our growth in 2008! You continue to show us that we're on the right track.
We know what is driving your use of Flock. You're life isn't slowing down. You're engaged and more social than ever before. You want to know what's going on and there's a lot you want to share. You've got more friends and you want to make sure you don't miss a thing. And sometimes that can be a bit much. No worries. That's how we'll continue to help, by making it easier for you to stay connected, but never tethered or walled in.
With a new year comes new opportunity and the entire Flock team is off and running to make 2009 great. We'll continue to go where your needs take us, and we'll do it by maintaining our commitment to innovation. While 'traditional' values like quality are important to us, Flock isn't like your parents' browser. At Flock we have a new world view of the browser and it's all about you.
We'll continue to innovate and find better ways to help you connect with the people, information and things you care about. But you're the best source of inspiration for Flock, so keep visiting the site and letting us know what you think and what you need. After all, at Flock it will always be all about you.
Thank you for a tremendous 2008!
Shawn Hardin
Tags: Flock, browser, growth, social actions
The giveaway has ended. Check out who won a free copy of Guy Kawasaki's "Reality Check"!
The following people have been drawn as winners of Guy Kawsaki's marketing bible, "Reality Check". Congratulations! The books will be sent out as soon as possible. :cool:
Hello all,
Just like for previous beta releases, I am going to guide you through the upgrade steps for Internet Explorer 8 Release Candidate 1 (IE8 RC1).
Before we begin, let me summarize the major changes you will see when installing IE8 RC1:
Note: If you are running Windows 7 Beta, you will not be able to install IE8 RC1. You will get an error message saying that your operating system is not supported since IE8 already ships in Win7. The IE8 RC1 available from Microsoft Download Center is a standalone upgrade for downlevel version of the OS only: Windows Vista, Windows XP, Windows Server 2008 and Window Server 2003.
Here are some additional resources you can refer to during the RC1 installation:
Getting Ready
Before you start IE8 RC1 installation, there are a couple of things to keep in mind:
If you have Internet Explorer 8 Beta 2 or prior installed, the IE8 RC1 installer will automatically uninstall any earlier versions and then install the latest version of IE8 RC1 for you. You will be prompted to reboot twice. The first reboot is to remove pre-RC1 version from your machine and the second one to complete the IE8 RC1 installation. When you launch Internet Explorer, you can open the Help->About Internet Explorer dialog to see the version number 8.0.6001.18372.
There is 1 update required when running IE8 RC1 on multi-core XPSP2 x86 computers:
KB932823 or KB946501 - This update resolves a problem in which an access violation occurs when an application exists on a Windows XP SP2-based multi-core computer. It will be installed automatically if you select "Install the latest updates" option in Setup Wizard. If this update fails to install successfully, IE8 installation will be blocked until you manually install this update from Microsoft Download Center.
The only time we encourage you to manually uninstall Internet Explorer 8 Beta versions prior to upgrading to IE8 RC1 is if you happened to install Windows XP SP3 after installing IE8 Beta.
To see if you need to manually uninstall IE8 Beta first, check these things:
Click on the Start Menu and then right click on My Computer and then click Properties
On the General Tab under System it'll say Microsoft Windows XP Service Pack 3
From the Start menu, open Control Panel and click Add or Remove Programs
Select Windows Internet Explorer 8 Beta and you are unable to click on the Remove button.
If you answered yes to both questions, you will be able to install Internet Explorer 8 RC1, but once installed, you will not be able to uninstall either IE8 or Windows XP SP3 later. The Setup Wizard will warn you prior to installation:
If you chose to continue, Windows XP SP3 and IE8 RC1 will become permanent. You will still be able to upgrade to later IE8 builds as they become available, but you won't be able to uninstall them.
To avoid getting into this situation, we strongly encourage you to follow these steps before installing Internet Explorer RC1:
See my earlier blog post on Internet Explorer and Windows XP SP3 for more information.
Windows Update
Internet Explorer RC1 will be offered to all Windows XP and Windows Server 2003 systems that have IE8 Beta version installed and have Automatic Updates turned on in 25 languages. A prompt will appear in the notification area of the Windows taskbar when IE8 RC1 is ready for installation. The language version of IE8 RC1 offered is based on your Windows Operating System Language version. For example, if your computer is running a Chinese Simplified or German version of Windows, you will be offered IE8 RC1 in Chinese Simplified or German respectively. For any other Windows languages outside of the 25 that IE8 RC1 is available in, Internet Explorer 8 will be offered to you in English. Again, this only applies to those systems that have IE8 Beta versions installed.
Localized Versions
When installing localized versions of Internet Explorer 8 RC1 on XP or Windows Server 2003 please remember that the base language of the operating system must match the IE8 language you are trying to install; otherwise the Setup Wizard will display an error. You can install IE8 RC1 English on any localized OS Version.
More information about installing localized versions of IE8 RC1 can be found in the release notes.
Uninstalling IE8 RC1
Getting ready
Before you start installing Internet Explorer 8 RC1, there are a couple of things you need to do to prepare your computer:
Based on the feedback we received from you, our users, we changed the install of IE8 to automatically replace the older builds as part of the installation. You are no longer required to manually uninstall IE8 Beta builds if you want to upgrade to IE8 RC1. All you have to do is run the IE8 RC1 installer and it will automatically replace the previous IE8 build with the latest one. You just reboot at the end, and you are done.
KB937287 - This update helps improve reliability and performance when you install or remove Internet Explorer 8 and future individual updates from Microsoft. Without this update, IE8 setup will be blocked: "Setup cannot continue because one or more updates required to install Windows Internet Explorer 8 are not present." To check if you already have this update on your system, go to Control Panel ->View Installed updates and search for KB937287.
KB957388 – This update addresses known application compatibility issues in Windows Vista. It will be installed automatically if you select "Install the latest updates" option in the Setup Wizard.
You are now ready to install IE8 RC1. After IE8 RC1 installation is complete, the final screen of the Install Wizard indicates that Internet Explorer installation completed successfully.
After you restart your computer and launch Internet Explorer, you can open the Help->About Internet Explorer dialog to see the version number 8.0.6001.18372.
Localized versions
In Windows Vista and Windows Server 2008, we significantly improved the installation experience for localized versions of Internet Explorer 8 RC1. Unlike Windows XP and Windows Server 2003, the base language of Windows does not need to match the Internet Explorer 8 language version in order for a successful install. When your user active language matches the Internet Explorer 8 language you installed, then IE8 will appear in the desired language. You will still be able to use IE8 in all other scenarios, but it will appear in English as a fall back version.
More information about installing localized versions of IE8 RC1 can be found in the release notes.
Uninstalling IE8 RC1
What do I do when I run into issues installing IE8?
Check out the knowledge base article on Troubleshooting IE8 installation. If after trying the recommended workarounds you still can't install IE8, go to the IE Beta Newsgroup to see if there are any known solutions available. Microsoft MVPs and IE Team members are monitoring this newsgroup and they will help address your issues.
Thank you,
Jane Maliouta
Program Manager
We're excited to make the IE8 Release Candidate available today for public download today in 25 languages for Windows Vista, Windows XP, and Windows Server customers. You can find it at http://www.microsoft.com/ie8. Please download it now and try it out. We welcome your feedback!
What's New
The team will post more about all changes between Beta 2 and RC. In brief:
We also made some changes to the user experience based on feedback. For example, based on data about how people use actually it, we made fitting more items on the Favorites bar easier. (Note that the IE8 Release Candidate is for Windows Vista, XP, and Server only; Windows 7 users will get an updated IE8 with the next update of Windows 7. Also, the Release Candidate of the Internet Explorer Administration Kit is available for download now.)
What's Important
IE8 focused on how people really use the web. Consumers want a browser that makes the tasks they do every day faster and easier. The activities people spend their time on define real-world performance: navigating to websites, working with tabs, searching, great interoperability, and a powerful platform that enables them innovate. For some people, accessibility is crucial; for some organizations, policy, administration, and deployment are essential.
The people who read this blog and comment on it are (for the most part) technology enthusiasts and professionals. We enjoy wading through the details of browser features or how to measure performance. We also need to remember that we're a pretty small minority of the hundreds of millions of people who browse the web. Looking at the telemetry data and usability tests and feedback from real users, we're excited about the positive impact that this release of IE will have.
What's Next
The call to action now is for the community to download the Release Candidate, test your sites and services and software with the product, make any changes necessary for the best possible customer experience with IE8, and let us know about your experience.
We're going to continue listening to feedback. We're interested in reports of critical issues (e.g. security, backwards compatibility, completeness with respect to planned standards work, or robustness). We're also going to keep blogging and reading and responding to the comments here.
Our next step, after listening to feedback from the final testing feedback from the community, is releasing the final product. We will be very selective about what changes we make between the Release Candidate and the final product, and very clear in communicating them. We will act on the most critical issues.
Books often have dedications from the authors at the beginning. While software typically doesn't have an equivalent, the software developer's blog is a good stand-in. To everyone who has installed the product and provided feedback so far – web developers, security experts, industry partners, IT professionals, and people who "just" browse the web – thank you from the Internet Explorer development team.
Thanks –
Dean Hachamovitch
General Manager
PS – Jason Upton and I sat down last week with Channel 9 to discuss the RC. You can view the interview here.
Updated 4:04pm – adding link to interview.
Hey Flockstars,
I just wanted to remind you that (nearly) every week I hold Community Office Hours on Monday at 11am PST.
While you're always welcome to contact us on GetSatisfaction, IRC, or by email (evan at flock dot com), I am often unable to talk in real-time during the week. Things come up...meetings, brainstorms, sudden bouts of synchronized dancing and singing, etc.
During Community Office Hours I am entirely focused on and available to the Flockstar community. Ask questions, give suggestions, or just send me awesome lolcat links.
I promise that from 11am-noon on Mondays I will not multi-task or get pulled into meetings. I may Tweet if you send me a really funny lolcat. No promises there.
My contact info is always available on my bio, but I'll repost here for your convenience:
email: evan at flock dot com
AIM: evanhprotean
MSN: evanhamilton_protean at hotmail dot com
Gchat: evanhamiltonLD at gmail dot com
Skype: evan.hamilton
IRC: irc.flock.com, #flock
Talk to you in a bit!
Evan Hamilton
Community Ambassador
evan at flock dot com
Tags: communityoffice hours, Flock, browser, community management, evan hamilton
Join the Mozilla Community Marketing Team!
If you're one of the more than 200 million satisfied Firefox users all over the world, we invite you to take the next step and join the Mozilla movement.
…notice this yesterday while running the Windows 7 Beta:
If you open the newly redesigned whitehouse.gov in Internet Explorer 8 on Windows 7 Beta, you'll notice that the dropdown menus don't hide correctly when you hover over other menu items.
This is because the version of IE8 in Windows 7 Beta is somewhat older than the Internet Explorer 8 Release Candidate (IE8 RC1) that we're about to release for Windows Vista and Windows XP. Internet Explorer 8 RC1 displays whitehouse.gov correctly - without this menu issue, as does most recent internal Win7 build.
Over the past months, our compatibility team has been hard at work, finding and fixing bugs that cause site rendering issues. Due to the different release schedules for Windows 7 Beta and IE8 RC1, some of these bug fixes didn't make it into Windows 7 Beta (aka Build 7000). So, if you want to use the latest version of IE8 – you'll want to install IE8 RC1 for Windows Vista or Windows XP.
Just like we did for IE8 Beta 2, we would love to get your feedback on IE8 RC1 rendering. Soon after we release IE8 RC1, we will blog again about using the Report a Webpage Problem Add-On to report site rendering issues. The data that you have uploaded with this tool in the past has been very useful in our efforts to find and fix rendering issues - thank you very much for helping us out.
Frank Olivier
UX and Compatibility PM
When I first connected myself to the internet, I was a simple guy with no information about firefox. Then I did not know what the firefox is.But after only 3 month of web use I found my scure browser Firefox. At first I was a little bit cautious about the security of this web browser, but now it is my regular browser. I have used many browser till now but just got stagged with firefox.
This week-end I flew all around the world [from Helsinki, FI] to head to Hobart, AU. I’ll be giving a talk at linux.conf.au titled “Contributing to WebKit”
As the abstract states, if you ever wanted to work on a big project that still has a relatively understandable codebase, come and learn how you can participate! The talk will be very much about the WebKitGtk and QtWebKit ports, but it will cover all aspects of contributing to WebKit.
We are here to create a FOSS community regarding the Mozilla Usage Community.
I would like you all to fulfill this target.
Any comments regarding the mission is always welcome.
Thanking you
Shashank Shree Neupane
Today marks an important day for Opera. We have reached more than 2 million registered users on My Opera - Opera's official community! :headbang:
When the two co-founders of Opera, Jon S. von Tetzchner and Geir Iversøy, did the first few lines of code which would eventually culiminate in the Opera Web browser, they only had their network and community to support and help them spread the word:
Want to hear what a Web designer from Netherlands thinks of society and life?
Want to hear what a Web designer from Netherlands thinks of society and life? Then this blog is for you. He is not only skilled with a mouse and keyboard, but also with the good 'ol paint brush! Just check out his painting of a Jaguar XJ
As some of you is getting more and more worked into Opera's awesome abilities, many discover new features you can't live without.
As some of you is getting more and more worked into Opera's awesome abilities, many discover new features you can't live without. One is the option to create a custom search and with a few keystrokes adapt it to your needs.
Go to Tools -> Preferences (Ctrl + F12), go to the Search tab:
http://www.imdb.com/find?s=all&q=%s&x=0&y=0Name: My Opera
Keyword: my
Address: http://my.opera.com/%s
Name: Wikipedia
Keyword: wiki
Address: http://en.wikipedia.org/wiki/Special:Search?search=%s
Name: YouTube
Keyword: yt
Address: http://www.youtube.com/results?search_query=%s&search_type=&aq=f
Feel free to add more searches, tips & tricks and other good stuff as a comment below.
Kudos Amnith for writing the blog post. :cool:
Check out these two cool "User JavaScripts" to further enhance your My Opera blogging experience! They are made by a very talented community member. :cool:
User JavaScript can be used for many purposes, including enhancing Web pages. To enable for User JavaScript you need to specify the path to a folder on your computer where these files are stored ("Preferences" > "Adavanced" > "Content" > "JavaScript Options" > "User JavaScript files").
To learn more about User JavaScript, please ou can double click the resize area to restore original dimensions.
Download power-drag.
This script adds a small menu which can be toggled by pressing ALT while hovering text (illustraton). The menu has many options, and the script is localizable (currently translated into English, Portuguese and Polish (credits to Wasacz).
Download power-meenoo.
Both scripts work great with blogging on My Opera. :)
Updates to the scripts will be done in xErath's
One nice feature of WebKit that has been integrated into Qt 4.5 is the support for full page zoom. It means that you would be able to scale the whole page and not only to make the text smaller or large. You can experience this already with the demo web browser if you grab Qt 4.5 beta. Go to a web site and use the View menu to actually zoom in and out everything, including the embedded image. This is achieved with a new property: QWebView’s zoomFactor. Whether the zooming is applied to both the text and images or only to the text can be tweaked via the appropri Along with this, I show a new example of capturing a web page. This is actually a request, as an alternative improvement to the web thumbnail example which has been shown before. Using it is as easy as: The code will run both with Qt 4.4 and 4.5. Under Qt 4.4, it will grab the contents of the page (www.trolltech.com), render it to an image, and then scale the image accoding to the zoom factor (50, in percent) that you specify, and finally save it to a file (trolltech.png). With Qt 4.5 however, it will set the zoom factor before rendering the page to the image, effectively skipping the need for the scaling process in the end. Both approaches have advantages and disadvantages. For zoom factors less than 100%, the scaling approach usually gives a much better result. However, it is more expensive since we always need an image (for the buffer) as large as the page size. Think of a really long page like Google News or Digg. On the other hand, for an obvious reason, image scaling will not work well for zoom factors more than 100%. If you want an extra exercise, do the following. Modify the capture tool so that it uses the image scaling method for zoom factors less than 100% and full-page zoom when the zoom factor is more than 100%. That likely gives the optimal result. Another potential use case for such a tool is to perform a quick visual check of web pages at different viewport size, for example when they are viewed in mobile devices. While most desktop and laptop stick to at least 1024 pixels wide monitor these days, many mobile phones are still using QVGA (320×240) and HVGA (320×480) screen. You can pass the viewport width as the fourth argument to webcapture. Shown below (click to get the larger version) is the mobile version of BBC Technology section rendered in three different widths: 240, 320, and 480, respectively. As you can see, the page still looks nice even if the screen is not that wide. The code is available from our brand new git repository for Graphics Dojo under the subdirectory webcapture. If you did a clone before, you just need an update. Otherwise just do the following: This example also demonstrates the often asked question: how do I know the height of a web page given the width? You might want to know this if you need to display the page without the scroll bars (which implies a viewport as large as the contents). The steps are as follows: load the page, disable the scroll bars, set the viewport size to a sensible one (only the width here matters), and then get the contents size. If you test this trick to e.g. Google News, you will get 768 as the height of the viewport but 3161 from the contents height. Thus, this gives you something like heightForWidth() function. Happy capturing! Back in October, Sunava described changes that we made to the XDomainRequest (XDR) object in IE8 between the Beta 1 and Beta 2 releases. This object allows your AJAX web pages to request data from sites with a different hostname from the page itself, something that IE doesn't allow for security reasons via XMLHttpRequest. Since Beta 1 we've been working with the W3C Web Application group on the Access Control framework and the changes we made in Beta 2 were to ad I'm happy to announce that we have recently completed our support for the Access Control Check using the Access-Control-Allow-Origin header defined by the updated spec. This means that, in addition to the wildcard check (looking for *) that we supported in Beta 2, we also now support the origin URL check. This support will be part of the next public release of IE that Dean announced a few weeks ago. I have recorded a short video that demonstrates how to use XDR and what this announcement means. It also shows how the Access Control framework is supported by other browsers allowing interoperable services to be called from your pages. If you'd like to download a copy of this video, it's available here. Adrian Bateman Update 3:55: Adding a link to a downloadable version.четверг, 15 января 2009 г.
Capturing web pages
webcapture www.trolltech.com 50 trolltech.png
git clone git://labs.trolltech.com/GraphicsDojo
Completing Access Control support for XDomainRequest
Program Manager
As a Program Manager, I love to write feature specifications (that's a job description requirement)! In each spec, PMs carefully weigh the pros and cons of certain design tradeoffs, consider the customer requests, available feedback and telemetry data, etc. Based on all of that information, we make certain informed assumptions about what we would like to build and how. Despite our best planning efforts, we know that some of the assumptions made in early specs may change at any time through development. One of these common ar
Responding to changes in web standards during the middle of the product cycle can be challenging for a variety of reasons. Speaking strictly from a development standpoint, feature changes always come at a cost—usually a trail of product bugs which take time to find and fix. Other changes are risky because the standard that they are based on could change. Each time we consider a change, we must carefully weigh the consequences.
In this post, I'd like to describe a significant recent event in the evolution of one web standard and how we chose to respond to it in Internet Explorer 8. I think this post offers a unique view into the complexity involved in responding to changes in web standards during development, as well as a great forum to announce the change in the upcoming release candidate.
ECMAScript 3.1
ECMAScript, the standard that defines JavaScript, was last updated almost 10 years ago. Earlier this year however, a revision that has come to be known as "ECMAScript 3.1" began to make rapid progress toward standardization. Back when we started work on Internet Explorer 8, we expected that any new ECMAScript developments would occur soon enough to give us ample time to integrate them into our planning; we were motivated to revisit that expectation with the recent rapid progress of ECMAScript 3.1. In particular, we wanted to be careful not to introduce features into Internet Explorer 8 in a way that would be incompatible with what we could see coming in the ECMAScript 3.1 draft.
ECMAScript 3.1 includes many extensions to the JavaScript language that make web development easier and more powerful. One of these features is JSON support and we quickly decided that the native JSON API in IE8 needed to be the same as the JSON API that is included in the ECMAScript 3.1 draft. Another feature from the draft that quickly came to my attention was support for getters and setters.
DOM prototypes
For many months we've been working on a feature that helps make the DOM more compatible with the JavaScript language by introducing the concept of JavaScript prototypes to the DOM. Using DOM prototypes, savvy web developers can easily extend HTML elements and other DOM objects with new functionality, develop more powerful libraries and abstraction layers, and even replace any built-in properties and methods with their own. This was one of our top-requested programming features by influential JavaScript experts. One very important part of the feature was getter/setter properties in the DOM.
Prior to 3.1, ECMAScript did not include the concept of getter/setter properties, but some JavaScript implementations did support them using an API that is mutually supported by several other major browsers and programming environments. When we started working on DOM prototype support, we chose to implement that de facto getter/setter API.
ECMAScript 3.1 made an early decision to include getter/setter properties but by using a more flexible API rather than the de facto API. This decision was made with the concurrence of all the major browser vendors including those who currently support the de facto getter/setter API. With ECMAScript 3.1 in full swing and other browser vendors bought-in, we now had an important decision to make: do we respond to this unexpected change and pursue implementing the ECMAScript 3.1 getter/setter API for the DOM, or do we ship what we have and tackle the ECMAScript 3.1 API in a future release?
The answer really came down to what was best for the web developer; they need interoperability and by ensuring that we support getters/setters as outlined in ECMAScript 3.1, we help deliver that interoperability in the long-term. Given that we were mere weeks away from shipping Beta 2 and did not want to put the quality of that release in jeopardy, we felt it was important to release the existing implementation (de facto getter/setters) to give web developers a chance to test and find any significant bugs rather than cut the feature from Beta 2 (saving it for RC 1). We appreciate the feedback we've received thus far, and have been able to take the requisite time to respond to compatibility issues that we might not otherwise have had the time to do.
Standards first
I'm now pleased to announce that with the upcoming Release Candidate of Internet Explorer 8, we not only have a high-quality DOM prototypes implementation, but we've been able to change the getter/setter implementation to follow the draft ECMAScript 3.1 standard. While our JavaScript engine and DOM won't have support for all of the ECMAScript 3.1 enhancements in this release, it does mean that web developer code written to add getters and setters to the DOM in Internet Explorer 8 will continue to work now and into the future, since that code will be based on web-standards.
I'm very excited about this new capability in IE8! To help you get started, I've written a few articles that provide an introduction to DOM prototypes and getter/setters (and the new syntax that will be publicly available in the upcoming release candidate build):
Also, some of you may have noticed that MSDN has also been updated to include the prototypes available in Internet Explorer 8!
DOM prototypes and getters/setters allow for some pretty cool programming possibilities. In an upcoming blog post, I'll get into more details on some of the scenarios that IE8 makes possible. Please leave a comment and tell us what cool scenarios you've already implemented using this feature!
Returning to the topic of responding to change, what may initially appear as the best design for the web may change over the course of a product's development. The experience I had with DOM getters/setters in Internet Explorer 8 has personally confirmed this. As we finish IE8 and on into the future, we'll continue to gather the right data, listen to customer feedback, and make product changes where appropriate. I know our team cares a lot about web standards and supporting them as a way to achieve interoperability—which ultimately helps web developers to be more productive; embracing ECMAScript 3.1 is one more step to help get there sooner.
-Travis Leithead
Program Manager
The Windows 7 Beta includes a beta of Internet Explorer 8. I say "a beta" because IE8 in Windows 7 Beta is a pre-release candidate build of IE: it's IE8 Beta 2 plus end user features that are only available on Windows 7 plus many fixes based on feedback we've gotten from IE8 Beta 2 usage. This post is an overview of what you'll find new in Windows 7's Internet Explorer, as well as some suggestions about how to get the best experience with this pre-release software.
Tabs are a very heavily used feature and Windows 7 makes it easy to switch to any tab you want. When you move the mouse over the Internet Explorer icon, you'll see a thumbnail image of every tab of every IE window that you have open. Just click the page you want to get back to.
Figure 1: IE Tabs in the Taskbar
Given that users open the browser with a specific destination in mind – whether it be mail, an online newspaper or even a search, IE8, in conjunction with Windows 7, introduces the new Jump List feature which makes 'getting where you're going' faster and easier. Jump lists help you get back to the most frequently visited sites in your history list even before you've opened the browser! These lists can be opened by dragging up (or right-clicking) on the IE icon on the taskbar. Clicking one of these will launch the IE browser and navigate to that site. Once IE has been opened, you will see the same drag-to-display functionality in the address bar. Simply putting the mouse on the text in the address bar and dragging down will open your most frequently visited sites.
Smart Address Bar is invoked with Touch, we put more spacing between items so it is easier to touch the link you want. We've also made the tab close button hit target taller.Here's an example of how the items in the Favorites Center are more spaced out when using touch.
Figure 3: Spacing of items in IE for use with touch
Touch also has a much more direct feeling than a mouse. When using touch machines, users naturally use their finger to scroll the page up and down, so we support that by default. In addition, navigating back and forward can be done with a left or right flick.
Other features enabled for Touch include opening a link in a new tab, which can be done by placing the finger on the link, dragging it a few pixels in any direction and then releasing, and two-finger zoom (on multi-touch enabled machines only).
Our data and experience signing-off on the Windows 7 beta has been positive. Many of us have been running Windows 7 as our primary machines at home and at work for a while and loving it. At the same time, we pay very close attention to feedback. We're looking forward to the data from millions and millions of beta users.
From the preliminary data we have already, we have some suggestions for people running the beta. The general advice is to run the latest versions of add-ons - we've been working with several add-on developers to make sure that together we're able to deliver the best possible experience and there have been quite a few improvements. Some specific recommendations:
There isn't an update for the HP Smart Web Printing Add-on available at this time. For this add-on, IE will show you the following message and ask if you'd like to disable this add-on. Choose "Disable this add-on".
Use version 4.0 beta not 3.0. For older versions of the Skype add-on, IE will show the following message. Choose "Disable this add-on". Then get the latest Skype version 4.0 beta which works well by clicking the "Check for updates" button or by visiting http://www.skype.com/download/skype/windows/beta/ directly
Use the latest version of Windows Live Sign-in Helper. You can get it from http://get.live.com/
There isn't an update for the Weather Channel Toolbar available at this time. If you experience problems, you can disable this toolbar by right clicking and unchecking the Weather Channel Toolbar.
Figure 4: Right click to disable a toolbar in IE
As we gather more real-world data about the IE8 in Windows 7 experience, we'll keep you updated here.
The IE8 rendering platform is the same across different OS's. So, you can write your page once for IE8. If you're using OS detection logic you need to make sure it works properly to account for Windows 7.
Check out the Engineering Windows 7 blog to learn more about Windows 7. I'm looking forward to your comments.
Paul Cutsinger
Principal Lead Program Manager
As announced in February 2008, Internet Explorer 8 sends an updated user-agent string when interacting with web servers. Since we last blogged about the User-Agent string, the Internet Explorer team introduced Compatibility View and today, the Windows team is releasing the Windows 7 Beta. Each of these events has a small impact on the User-Agent string, as I will outline in this post.
In order to help users visit sites that block the "MSIE 8.0" user-agent string, IE8 will send the "MSIE 7.0" version information when viewing sites with Compatibility View enabled. As Scott described last August, a new "Trident" token in the User-Agent string allows your code to detect Internet Explorer 8 clients even when they are using the Compatibility View feature.
IE8 on Windows Vista (Compatibility View)
Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; Trident/4.0)
Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.0; Trident/4.0)
As noted in the Best Practices for detecting the IE version, we recommend that web developers do not block access to content based on the user-agent string of the browser. If you must offer different content to different versions of the browser due to improved capabilities, you should ensure that future versions of the browser are not blocked.
Serving content based solely on the user-agent string is often an unreliable way to detect the full capabilities of the browser, because the user might have adjusted some settings, such as disabling script or extensions.
On Windows 7, IE8 will send the User-Agent string with the new Windows NT version token.
IE8 on Windows 7
Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0)
(If you're curious about why Windows 7 uses the version number "6.1": the short answer is that it improves compatibility, and the longer answer can be found over on the Windows Team Blog.)
Nevertheless, the "Windows NT 6.1" version token may still result in problems for a very small number of websites that check the operating system version. Such websites may show error messages or otherwise interrupt visitors who are running Internet Explorer 8 on Windows 7. The Compatibility View button will not resolve this problem for such sites, because the Compatibility View button only changes the Internet Explorer version number, leaving the Windows version number intact.
In order for IE8 users on Windows 7 to visit websites which block the "Windows NT 6.1" version string, a registry override must be set to temporarily change the reported Windows version number. If you encounter any websites that block Windows 7 visitors, please submit a bug report on Connect or provide the URL of the site in the comments below.
As machines with more than 4 gigabytes of RAM become more common, more and more users are running 64-bit versions of Windows. For compatibility with 3rd party add-ons, the 32-bit edition of Internet Explorer remains the default on 64-bit systems. However, in some cases it can be useful for websites to recognize when users are visiting using 64-bit systems—for instance, a site may want to know whether to offer a 64-bit executable download.
Tokens in the User-Agent string will enable you to determine whether or not the user is running a 64-bit version of Windows, and whether they are running the 64-bit edition of Internet Explorer.
64-bit IE on 64-bit Windows:
Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.0; Win64; x64; Trident/4.0)
32-bit IE on 64-bit Windows:
Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.0; WOW64; Trident/4.0)
Incidentally, WOW64 stands for "Windows on Windows 64-bit."
As described in the MSDN article Understanding User-Agent Strings, it is possible for users or applications to add new tokens to the User-Agent string by setting registry keys. We strongly encourage discretion in adding additional tokens, as the network overhead can become measurable as the string grows. Remember, the User-Agent string is sent in the headers for every HTTP/HTTPS request from the browser (and applications based on the IE Web Browser Control), so if you must add a token, please keep it as short as possible. We have also encountered some websites that do not function if the user-agent string is unusually long (for instance, over 128 characters).
You can check the User-Agent string your browser is currently sending here.
Thanks!
Eric Lawrence
Program Manager
Update 12:37: correcting formating of titles in post.
Meet a visual artist, web designer, guitar player and writer from Italy who has been around for a while and has a great Flickr style themed blog. :D
Meet a visual artist, web designer, guitar player and writer from Italy who has been around for a while and has a great Flickr style themed blog. :D
Being a visual artist and well established Web designer he plowed through My Opera looking
The Weblog Awards are the world's largest blog competition and My Opera (thanks to Postman Pechkin) is a finalist in the "Best Online Community" category. You can help My Opera win by submitting your vote today! :cool:
2009 is officially on and we've gathered a small collection of great fireworks pictures. These images are all found on My Opera from the community section. Enjoy. :)
2009 is officially on and we've gathered a small collection of great fireworks pictures. These images are all found on My Opera from the community section. Enjoy. :)