Skip navigation.

exploreopera

| Help

Sign up | Help

Slightly ajar

Opening the web, one site at a time.

Posts tagged with "Open the Web"

Racing by for a podium finish

, ,

We're on a roll. Thanks to the great guys (and girls) at Turner, we have our second known fix of 2007. Added to the fixes we don't get reported, this isn't too shabby for the first few days back after the biggest hangover day of the year. Fittingly for the speed in which they fixed the issue after having it reported to them, the site in question was NASCAR. While in general the site, and other Turner properties like CNN, work fine in Opera, there was a minor problem on the news headlines page. The Inside the Numbers table was misplaced in Opera due to font size differences, which caused it to overlap with the text. This is corrected now, and everything looks great.

A big thank you goes out to the Turner and NASCAR team, and we hope they have a great new year. If anyone finds any other issues on the NASCAR site, then feel free to leave me a comment, with how to reproduce the issue, and we'll look into it.

Four countries, three states, one goal

, ,

After a long last minute trip, I'm back at Opera headquarters. Last week, I received a mysterious e-mail from Microsoft requesting that I fly out to Redmond, together with a party of our developers whom had a pre-planned engagement there. Their flight was due to leave the day after next, so after a rush to book tickets on any flight that was available, via Paris, France and Atlanta, Georgia, I was on my way.

We were hosted in the Microsoft Campus at the Platform Adoption Center (PAC). This facility hosts the Vista application compatibility lab, that works with 100,000 ISV's to help them get their applications ready for Vista. The main party was invited there by the Strategic Relations Group, where Microsoft works with rival companies to ensure they are treated fairly. Microsoft were very friendly, and we had numerous meetings with people working on Vista. A highlight was meeting up with the IE team over coffee and then lunch. Maybe people will probably want me to say they are satan embodied, but they are great guys and really do care about standards. We all got on like a fox house on fire.

Our programmers found a number of bugs both in Opera and Vista during the visit, and we made huge strides in Vista compatibility. We even got as much pop, and ice cream as we could eat and drink. This wasn't my focus however; Anne and I were invited for a different matter entirely, of which I'll post more about soon, so stay tuned.

Fashionably late to the party

, , ,

Never letting being late get in the way of a good story, I'd like to celebrate the launch of Opera 9 this past Tuesday. During the launch I was away in Germany at the World Cup match between England and Sweden. It was a great match but I was a wee bit guilty that I was there having a great time while other people were slaving away with the big launch. Although along with Mike, I've put a great deal of work in trying to get sites ready for the launch, be it through contacting sites, patching or working with developers on their issues in Opera 9.

Site patching is a difficult business as we like to give sites time to respond before applying a patch or user agent spoof, so not every patch needed for major sites was included for the launch, especially as we've been away in recent weeks to meet with developers, but they will be applied in the coming days. User agent spoofing can also cause unwanted side effects, such as a recent change with masking as Mozilla on my.yahoo.com. While this fixed three issues it was put in to fix, it broke another part of the site, where links now always open in a new tab due to the use of a Mozilla only property.

I've seen a number of of forum posts by people that say Opera 9 was not ready for launch, and indeed there are some issues reported by web developers I've been working with that have not been fixed. Although there are some issues, there will always be bugs in even the simplest of software applications (and a browser is far from being simple), and as the old adage goes real artists ship. While I'm sure everyone would have liked more time to work on Opera 9, it is a much better product than Opera 8 and we had to ship it sometime. I think the benefits of releasing it now outweigh the cons. Having the browser out there in the wild as a none-beta product will push developers that only support released products to add support for Opera in sites that require Opera 9 such as rich text editing or sites that broke due to a bug in Opera 8 or below. Opera was also delayed slightly due to the great effort put in by the developers to add support for DOM level 2 style such as document.stylesheets. This is used by a lot of important sites and I for one am glad we managed to get it included for the launch. I think I'm right in claiming that Opera is now the first browser to support all of DOM Level 2. That is a big thing and a few bugs shouldn't overshadow it

Not that bugs are unimportant. Far from it. Work continues on fixing known bugs and important ones will be included in the first point release of Opera 9. I'm still talking with sites and script authors on fixes that are needed on our and their side to work in our browser. I'm confident important open issues will be fixed soon. Nothing should detract from what is a top quality product, in my opinion, and the passing of the ACID 2 test and our support of the DOM level 2 spec is testament to the quality of our rendering engine and our commitment to web standards and a open web.

After partying with Monica and co, It's time I sign off and get some sleep, I've got a web to open in the morning…

@Media 2006 London

, , ,

business cards from @media, including AOL, Yahoo!, MSIE, Cameron Moll and Rabbit Design

Many useful contacts from @Media

@Media '06 has just been and gone. The event was like a who's who of the web design and development field. I was fortunate enough to attend this year and seen many interesting and informative talks by the likes of Eric Meyer, Nate Koechley (Yahoo!), Cameron Moll, Dave Shea (CSS Zen Garden), Tantek Çelik (Technorati, Microformats and former developer of IE Mac), Chris Wilson (Microsoft), Stuart Langridge, Jeremy Keith (Clear: Left) and Dan Cederholm (SimpleBits) amongst others. The social events and between talks were great for meeting new people, and importantly for Open the Web, finding contacts to report web site issues. I'm hopeful that I've found some people that can help me fix some long standing web site issues that effect Opera.

One of the nice parts of the trip was meeting people face to face that have and continue to help Open the Web. Nate Koechley of Yahoo! is one such Open the Web hero that has done more than many to promote open standards and get web sites working in as many browsers as possible. You may know him for his article on graded browser support as well as his work on the Yahoo! User Interface Library. If there was a Open the Web Allstars Hall of Fame, he'd be one of my first recommendations to be inducted. Stuart Langridge was another guy I bumped into that has helped us in the past with an addEventListener issue that keeps popping up on many sites. There was also time to meet new people such as Cindy Li, self titled Styleguide Princess of AOL and designRabbit.

One of the most interesting talks of the conference was Cameron Moll's presentation on Mobile Web Design. It turns out that he is a big Opera Mini fan and Eivind, Fred and I had an interesting chat with him afterwards on how we see the mobile web moving forward.

As well as the talk there was time to walk around London and see the many sites it has to offer. some of the architecture such as the Big Ben clock tower, the Tower of London and St Paul's were simply breathtaking and very inspiring. it's a shame we don't build stuff like that anymore. We wrapped up with some food at Wagamama. It is a chain of noodle restaurants that is not only great food and fairly cheap, but has great branding, design and has a seating arrangement that is designed to get people to mix and chat to the other people sitting next to you. Did I also mention it was tasty food?

Next stop on the Open the Web train is Köln, Germany tomorrow…

Open the Web Korea

, ,

We've been very active recently in finding issues on Korean web sites, and reporting these to the site authors. Korea is a quite unique market in that they have very advanced devices and one of the highest take up rates of broadband internet access in the world, yet Internet Explorer has a huge market share in Korea, so almost every site I've tested is designed and tested for IE and Windows only, without use of web standards. This causes big problems for every other browser and platform, including Firefox, Safari and ourselves. Some issues are bigger with no easy solution such as the use of Active X, but the majority are due to making use of quirks and bugs in IE and often only need to change one word to make them work in all major browsers. Many of these issues can be found in my previous post on common web site issues.

We'd like to do all we can to fix these issues and promote web standards, enabling Korean sites to work on any device, any platform and any browser. Users should be free to make their own choices on how they access the web. To help our push in this area we are extending Open the Web's efforts into Korea. Opera's team in Korea is growing as we speak, and Irene has recently been hired with part of her responsibility to work with myself and the rest of the team on Opening Korea. I'd like to wish her welcome, and look forward to seeing cross browser development take off. If you are Korean and can't access you're favourite sites, feel free to contact me and I'll make sure the issues get looked into.

Open the Web Japan

,

Since yesterday, we've expanded Open the Web's reach. I'd like to personally send a warm welcome to Michael Smith, who has joined our Open the Web team. Micheal will be based out of our Tokyo office in Japan and has extensive knowledge of the mobile web after previously working for Openwave, among others. He is also fluent in Japanese, which will help us greatly.

After he has settled in I'm sure you will be seeing more of him and might even get chance to talk in the Open the Web forum. It's good to have him on our team.

Buildup: New York Times Vs. USA Today

, , , ...

New York Times Vs. USA Today

In honour of the recent redesign of the New York Times, I'm starting off the duelling contest between a clash of Newspaper titans. USA Today is the top selling newspaper in the United States with a circulation of 2,154,539, while the New York Times comes in third with 1,118,565, according to Infoplease. I didn't choose the Wall Street Journal as it mainly focuses on business, so it it probably best to pair it up with the Financial Times at a later date.

I've contacted both parties today and I'm awaiting their response. I'm hoping they will be willing to work with us to improve any issues found. If I don't hear anything by this time next week then I'll start the contest, otherwise I'll delay until the contestants have time to make their pre-fight preparations. I'll keep you informed with any news and pre-fight quotes from either camp. May the best site win

The pages chosen to be compared are as follows:

These pages will be used for most of the criteria, but as many pages as possible will be used to test site compatibility, to ensure as many issues as possible are found. All web site bugs found will be reported to the site before the score for the first round is given, unless they make clear they will not make any changes.

Update on addEventListener

, , , ...

You may remember if you've been following my blog that a bug in the way other browsers implement addEventListener causes Opera problems in many web sites as they assume the broken behaviour. I updated that post to mention that Geoffrey Garen at Apple has reported to me that they have fixed this in WebKit. The issue has also been reported here in the Mozilla bug tracking system, and Jonas has stated that they will also fix this bug.

What does this mean for Opera? Well initially nothing, as all the broken scripts will still be broken, however once the browsers start rolling out with these fixes in place all new browsers will break on these scripts. The authors will begin to notice what we've been telling them all along and they will have to fix their scripts or not work at all in any new version of the browsers that support this method.

I'd like to thank both Apple and Mozilla for looking into this issue. The browser is quite a unique market where even though we are rivals, there is a lot of friendly co-operation between vendors and generally very little hostility. The WHATWG is a good example of this cross browser co-operation. While everyone wants to be the best browser, with the best standards support, no one will use them standards unless a majority of the other browsers also support it (unless your name is IE). Therefore you are in a strange situation where you want your rivals to improve their product so that people will actually start using the cool new feature you've just added. However strange this is, it is good for the industry and good for users as co-operation pushes the web forward and keeps it from splintering further into many single vendor solutions

How the points will be awarded

, ,

With any good contest there needs to be a winner, and thus a scoring card to rank each criteria. Below is the draft score card for the web site duelling contest. keep in mind that this may change depending on comments and if I find it is not quite suitable when assessing the sites.

Does the site work in all major browsers?

The most important thing, along with accessibility and usability, for a web site is that it works in all major browsers. The whole reason we have standards is to help make sure sites work no matter what choice of browser we choose. I will test the sites in four browsers, IE, Opera, Safari and Firefox. I would also test in Konqueror but I do not have constant access to Linux/Unix/BSD. Five points will be awarded or each browser the site works in, with a bonus of ten points if it works in all four. Points will be deducted depending on how many minor display, major display and major functional issues are present. A bonus of four points will be given to the winner of the round.

Total possible points: 34 points

Does the CSS and (X)HTML validate?

It is more important for a site to work in all browsers than to validate, but it is still the most important and useful tool to help make a site work in multiple browsers as it makes it easier for each browser to know how the page should be rendered. Ten points will be awarded for valid (X)HTML not including validation errors due to issues in the validator. Zero points will be awarded for fifty or more errors, with a scale in-between. The same scoring system will be used for CSS. CSS 3 is accepted so validation errors due to the use of this will not count as an error. As validating to a strict document type is more difficult due to less legal tags then a ten point bonus will be given if the page is valid with a strict document type. Two bonus points for having the lowest issues in CSS and two for the lowest in (X)HTML will be awarded.

Total possible points: 34 points

Are there any JavaScript errors?

It is much harder for authors to judge the quality of their JavaScript due to no validator, but using the JavaScript error console can help as it shows the issues the browser is having with the scripts. Ten points will be awarded for no errors, and zero for ten or more, with a scale in-between. This will be tested in all four browsers, with any duplicates still counting as one. Two bonus points will be awarded for wining the round.

Total possible points: 12 points

Does it use CSS or table based layout?

Table based layouts are the old way of web design, while CSS is the sleek modern method. The advantage is that the pages are often much smaller and more flexible with CSS layout. They are more flexible as the presentation is taken out of the HTML document and a page can be completely rearranged with a alternative stylesheet such as for handhelds or just an different look. Ten points will be awarded for a CSS based layout, a layout with minimal tables just for laying out the basic structure, such as three columns and a header, will get five points, and any more tables will get zero points. Tables for tabular data will still be allowed. A bonus of two points for winning the round will be awarded.

Total possible points: 12 points

Does it use CSS for style or HTML tags?

CSS styling should be used as it decreases the page weight and time taken to update the page as all the style information is in a separate file which can be changed once to effect the entire site. It also allows complete redesigns to be much easier or alternative stylesheets. With HTML style tags it is much more difficult to change the style of a page without re-coding the page. Ten points will be awarded for no sstyle based HTML tags, with zero for ten or more and a bonus of two for winning the round.

Total possible points: 12 points

Is the (X)HTML semantic and lightweight?

Having lightweight code instead of tag soup is important as it will load faster, and cost less to download on mobiles, as well as saving the company money on bandwidth. Having semantic markup is important as it help humans as well applications to understand the meaning of the content; Google for example uses the H tags when ranking pages, an they can be used by screen readers to add emphasis. With the semantic web in the future, having clean semantic code will become more important. Two points will be awarded for the correct use of h and p tags, two for using no extra div tags than are needed, two for the use of tags such as cite, q, blockquote, abbr etc., two for meaningful semantic names for classes and IDs, and two points for using lists correctly, such as for menus. Two bonus points will be awarded for the winner of the round.

Total possible points: 12 points

Does the page work without plug-ins?

Not all devices or platforms can use all plug-ins, and plug-ins such as Flash can cause accessibility issues. Therefore it is best if an alternative is given when plug-in content is used. Ten points will be awarded if the site fully works without plug-ins, except issues that reply on them such as playing a movie or sound clip. Five points will be given if there are two or more issues, two points if the site doesn't work but there is a warning, and zero if the site just doesn't work. Two points are again awarded to the winner

Total possible points: 12 points

Does the page work without JavaScript?

JavaScript can cause accessibility issues as well and an author can not rely on it being turned on, therefore all core functionality should have a fallback, such as server side validation. The same scoring system will be used as the criteria above, except progressive enhancements that could not be done without Javascript, as long as it remains accessible and are not core functionality, will not count as issues.

Total possible points: 12 points

Does the site follow accessibility guidelines

Accessible web sites are very important as information should be available to users online even if they are disabled. There are also government guidelines on the subject and making a site accessible helps with designing for mobiles and devices as well. The W3C WA guidelines will be used, with twenty points for passing WAI-AAA, fifteen for WAI-AA, ten for WAI-A and a varying scale to zero for issues in the site. A bonus of four will o to the winner of the round.

Total possible points: 12 points

Are decretive images included in the CSS instead of the HTML?

Putting none essential images in the CSS file has advantages in that they ill not be loaded f another stylesheet is used. This makes changing designs easier. It also means mobile browsers wont load the images, which saves bandwidth costs and doesn't break the layout</p?

Total possible points: 12 points

If a print option is offered is it a stylesheet or a separate page?

Using a print stylesheet ensures the print version will never go out of sync with main article. A print stylesheet can allows the author to have more control on the designs of the print option. Ten points will be given to a print stylesheet that validates, with five points for one that don't validating, then the points scale to zero depending on how many issues or if there is no print stylesheet.

Total possible points: 12 points

Is a handheld stylesheet offered or the site mobile friendly?

Handheld stylesheets for mobiles are useful as it allows the author to only write a page once then give a CSS file to customise the display. It also allows content to be hidden that is not needed for mobiles,and it wont be downloaded. Ten points will be awarded for valid handheld stylesheet which works correctly, five if the site useable but no stylesheet and doesn't look too broken. Less points are given for sites which have big issues or do not work on mobile phones.

Total possible points: 12 points

After all the points are added together the winner will be found. The highest possible score including winning bonuses is two hundred. Comments on the scoring system are welcome before the duels start.

The main event

Do you remember the Cola wars of the '80s? Coca-Cola and Pepsi went head to head in a battle of the titans to see who would become crown prince of the soft drink world. I plan over the next few weeks to bring this battle back and with many others, but not on how good they taste, how much they sell or their hip factor. Instead I'm going to set up duels between the top products or celebrities of their field, but with only one condition -- who has the best web site. There will be no relation to if like, support or buy the product. I've not fully settled on the criteria for best site yet, but it will be more related to compatibility, accessibility and good quality code than design which can be very subjective. The aim is to both learn what needs to improve in big popular sites, find the issues in them that we need to fix and hopefully to influence sites to improve; after-all they don't want to be slam dunked by their nearest rival do they?

The criteria I'm thinking about are as follows. Please leave comments if you've got ideas to improve these.

  1. Does the site work in all major browsers? (IE, Opera, Firefox, Safari)
  2. Does the CSS and (X)HTML validate or use standards based code the validators do not recognise yet?
  3. Are there any JavaScript errors?
  4. Does it use CSS or table based layout?
  5. Does it use CSS for style or HTML tags?
  6. Is the (X)HTML semantic and lightweight?
  7. Does the page work without plug-ins?
  8. Does the page work without JavaScript?
  9. Does the site follow accessibility guidelines such as alt tags on images
  10. Are decretive images included in the CSS instead of the HTML?
  11. If a print option is offered is it a stylesheet or a separate page?
  12. Is a handheld stylesheet offered or the site mobile friendly?

Not all of these will be yes or no answers, as clearly a site with one bug is better than a one with ten, and a site that works in four browsers is better than one that only works in two. I've also not decided if all criteria will be equal, but the site working in more browsers and being accessible are likely to be worth more than others that look at the quality of the code. If a site doesn't work because of a known bug in a browser then it will not effect the score unless it is easy to work around. If an issue is found to be a bug later then the score will be re-evaluated.

The ideas I have so far for web site duels are as follows. Any other suggestions are welcome.