Skip navigation.

ODIN Blog

Opera Developer Network

The lengths to go to, to get a site fixed!

,

There is this site, which had some very archaic code, which blocked Opera. Incidentally, that site is very big in India, and consequently, was India's most reported site compatibility problem regarding Opera. We quickly figured out what was wrong in the JavaScript code, and now it was only a matter of letting them know what's wrong so that they fix it and unblock Opera.

They had contact information on their site. First I tried their online contact form. No response. A few days later, I tried another contact form, again no response. Hmmm....

Then I found out a few email addresses. I wrote to them, including their webmaster address. Still no response. Then I thought, I might as well give them a call. On the phone, the person asked me to write to a different email address, so I did that. Still days later no response :frown: Called again, and finally got the number of the project manager of the site, and discussed the solution with him. He seemed supportive, and gave his personal email address, and requested me to email him with the solution again. Did that. Still no cigar!

A few more calls were made, with promises that the site would get fixed. Nothing happened. My only last hope was to meet them face to face.

I was going to that city in the near future for some conferences, and I thought I'll stop by their office as well. Well, the site in question belongs to a large financial entity, and had a LOT of security at their headquarters. They scanned me, my wallet, my bag, my laptop, made a note of which laptop i was carrying, verified with the people I was going to meet that I indeed was scheduled to meet them, and gave me a slip which I had to sign from the people and hand it out to the security when I walked out the building as proof that I indeed met them. All in all, I think I had to go through around 5 layers of security, of various types. No, I'm not joking.

Anyway, I got to the meeting room on the first floor and realized I had the edited source code with me in Opera (I had edited it to see whether the solution works). To show them the problem, I needed to refresh the page so that the original source code was available, and change it once again in front of them to show how to fix it. However, wi-fi wasn't available, and no ethernet cord was there in the meeting room as well. So they did the next best thing.

They printed out the source code of the pages in question and gave it to me. So now I have their site source code on a bunch of paper, and a pen which they graciously offered me, and had to explain what was on wrong in their own source code and how to fix it by marking it with pen and paper. Great!

Finally I did that, and I was glad that they finally got the solution. They were quite pleased to know that Opera pays so much attention to site compatibility and that we have a dedicated team for it. A few days later I got the news that they had fixed the issue, and the site no longer has the code which blocks opera.

The lengths to go to, to get a site fixed!

Opera Mobile 10 and its remote debugging party trick

, , ,

Following on our Opera Mini 5 beta launch, we've just announced the release of another mobile browser — this time it's Opera Mobile 10 beta for Symbian. While they both feature a similar redesigned UI, Opera Mobile 10 makes the most of your smartphone's capabilities, featuring a full JavaScript and layout engine.

Naturally there are many improvements for mobile surfers to enjoy, but what will be of particular interest to developers are the enhancements to Presto, our rendering engine. Not only is it much faster than the previous incarnation of Opera Mobile, but you may also be impressed at its standards support. You can read more about Opera Mobile 10 from a developer's perspective over at dev.opera.

In addition there is one more feature aimed at developers that we're particularly proud of and that is the ability to remotely debug a web page on your mobile phone using Opera Dragonfly on your desktop. Put more simply, as you edit the web page's code on your desktop, its display is dynamically updated on your mobile phone. The process is as follows:

  1. (Desktop): Make a note of your local IP address and fire up Dragonfly.
  2. (Desktop): Enable remote debug in Settings and click Apply then OK in the pop-up dialog box.
  3. (Mobile): Open opera:debug, enter your desktop's IP address and click Connect then OK in the pop-up dialog box.
  4. (Desktop): Click OK in the pop-up dialog box to download the new version of Dragonfly, then click OK.
  5. (Mobile): Click Connect again in opera:debug, then click OK in the pop-up dialog box.
  6. (Mobile): Open the web page you want to debug, ideally in a new tab.
  7. (Desktop): Select the site to debug in Dragonfly and edit the HTML and CSS to your heart's content.




We've made a short video to show remote debugging in action with captions for people that suffer from deafness/limited hearing (or if you just want to watch it without disturbing those around you). Furthermore, the captions are also available in English, Japanese and Russian.

Tomorrow's web standards today - British Computer Society presentation, Surrey University

, , , ...

I had the pleasure of speaking to a really savvy crowd at Surrey University last night on "Tomorrow's web standards today".  It was a fun session with lots of really good questions at the end - just the way I like it.

Below are my slides written in HTML. They're best viewed in Opera on full screen (View > Full screen) but of course work in any browser.Demos for <video>, <canvas>, SVG, web forms, widgets and media queries are all either linked from the presentation or bundled together in the download.

Tomorrow's web standards today, 6.8MB

Run Opera Widgets as standalone applications

, , ,

Over at Opera Labs, we have just released a desktop build that allows you to run Opera Widgets as standalone desktop applications. With this release, widgets are getting a complete make-over from being small, single-purpose gadgets to first-class citizens with the power to replace native applications.

Differently phrased, this means that any web developer with knowledge of HTML, CSS and JS can create a desktop application. And for good measure and scaling goodness, you can even throw in some SVG magic as well!

Below, I've included a screenshot of my Mac running the Twitter widget. Note the Twitter icon shown in the Dock, the native Chrome and shadow, and the fact that Opera is not running.

Screenshot of standalone Twitter widget

You can find detailed information about installation, running, debugging widgets on this Labs build on Dev.Opera. If you want to get started building your own widgets, there is of course our Widgets SDK.

Note: there are currently some issues to get the Widget Emulator running well on Opera 10.10 builds – we are investigating this and working on a fix. For the time being, we recommend to use the Widget Emulator in Opera 10.

And of course, let us know what you think in the comments!

Opera 10.10 beta with Opera Unite has landed

, , ,

Almost four months after its initial Labs release and several snapshots later, we’re happy to announce our Opera 10.10 beta with Opera Unite.

For this release, we’ve brushed up our Opera Unite developer primer, and Zi Bin has written an introduction to Yusef, the Opera Unite Server framework.

Shwetank has also been working on building his own Opera Unite Task Manager application — see his earlier entry on the ODIN blog for more details and some handy tips.

Note that this release does not include a fix for the @font-face font descriptor bug just yet. We’re still working on a fix, but it takes a bit longer than expected.

So, check out the video for this release, play with the beta release, and get started with building your own Opera Unite application. And of course, let us know what you think on the Dev.Opera forums.