palbo

How do you feel about your US market share?

What US market share? ;-)

Do you guys actually use Opera dragonfly or do you resort to firebug like the rest of us?

Yeah, mostly, i'll use firebug and the webkit inspector too sometimes, but i don't usually debug js heavily, just very casual use.

Is it just me or does it take 1+ mins for some prefs to be saved? For example: edit site pref > cookies > edit

Not for me, you should report a bug.

What does this setting mean: opera:config#Network|AllowCrossNetworkNavigation. Why isn't the documentation up to date on these things?

It's some obscure network thing, if i remember correctly for a case where a site on the internet needs access to a site on an intranet, mostly noticeable in some corporate environments. Most of those prefs are not documented because some of them shouldn't even be visible to normal human beings... there's differing views about this within the company :-)

Heh, that's bug CORE-1 (i.e. a very very old bug, dating from the year 2000).

I think there are surprises in store on that front, although i can't say for sure, and i'm probably not allowed to disclose that anyway.

We have a task force of sorts that deals specifically with fixing bugs in the browser that affect site compatibility (known internally as the sitecompat task). We call site compatibility to bugs that stem from all the major browsers (including us) doing something differently from the norm, which leads to perceived problems with sites, this sometimes means that we're following the standards and other are not, or viceversa.

It's not always our fault either, but all of this is put in the balance when deciding how to fix a particular issue.

There's also a thing called browser.js, which is "opera sponsored" userjs, sometimes used as a quick way to fix a problem temporarily, effectively patching the site, until we can get a proper fix in place.

Another way we have of dealing with this is the Open the Web team (OtW), these are the guys that get in contact with webmasters when the actual problem is that the site is doing things "the wrong way", be it by doing things in a browser specific way, or not dealing with some opera specific thing or whatever. So they get in touch with them and help them fix the issues on their side, basically spreading standards awareness (in general).

I spent a while working on bugs for that task, so i should know :P

Why haven't you properly implemented onunload?

Why haven't you implemented onbeforeunload?

Our current code architecture makes these two particularly difficult to implement properly, so it's very non-trivial (the features itself are fairly trivial, just not in our codebase the way it stands to this day), it's just stuff that happens when you accumulate code for a decade and a half. It's also usually not prioritized very high in comparison to other features, but it's not in the bottom of the pile either, it will eventually come.

Why haven't you implemented pageshow/pagehide?

See this post.