Opera Desktop Team

First Weekly Builds

By Trond. Monday, 13. February 2006, 16:11:29

Here are the first weekly builds made available on this blog. UNIX builds are missing this time.

Download links
Windows build 8219
Mac build 3224

Release Notes

Fixed some NTLM proxy issues.
Added ability to save to disk from source viewer.
Improved handling of plug-ins when no data attribute is specified.
Removed support for "javascript:" URLs in CSS.
Several fixes for the position style.
Corrected encoding when redirecting e-mails.
Fixed an issue with favicons.
Fixed :required :optional :read-only :read-write and :default pseudo-class selectors.
Improved handling of the autofocus attribute from Web Forms 2.0.
BitTorrent fixed on Mac.

Welcome to the Desktop TeamMaking love to the new feed icon

Comments

dan1el # 13. February 2006, 16:41

Nice work. *Downloading*

sebt # 13. February 2006, 16:50

Sweet

Does it fix the table/layout bug when refreshing on myopera forums and other forums?

I've also seen table layout weirdies on other sites at tp2.

See http://my.opera.com/community/forums/findpost.pl?id=1424328

Seb

LordDaimos # 13. February 2006, 17:12

There still seems to be problems with the NTLM support. I know I enter the correct password in the dialog (works fine in IE or if I disable NTLM) but it just keeps reappearing for me and I won't get authenticated :/.

/ Karl

Ravindran # 13. February 2006, 17:18

Same here. Still finding problem with NTLM.

Pondus # 13. February 2006, 17:28

May I ask for a more specific description of the fixed favicon issue?

sebt # 13. February 2006, 17:40

Seems that the table layout bug is still there. On occasion, when I refresh at www.mininova.org, all the table columns are the wrong size.

Seb

KvaZaR # 13. February 2006, 17:40

Very nice idea about weekly updates!

tarquinwj # 13. February 2006, 17:50

IIRC, the favicon issue related to favicons that are sent with the wrong content type (many apache servers default to text/plain for favicons)

non-troppo # 13. February 2006, 17:56

Pondus # 13. February 2006, 17:58

tarquinwj: Seriously? I believe this fix will close several bug reports reported by me. Talking about a great monday

davidcrickett # 13. February 2006, 18:00

None for Linux (Ubuntu)?

csant # 13. February 2006, 18:10

davidcrickett,

see here...

tprochazka # 13. February 2006, 18:14

This version crash, when I use search in opera:config screen.
TP2 not.

MarkGillespie # 13. February 2006, 18:15

Nice, no fixes for the crashes when checking newsgroups thou :-( I get 15-20 crashes a day from this. So bad I had to revert to 9.0tp1..

Will keep an eye out, see if it crops up in the fix list. Would really like to run the latest code, as tp1 has it's own set of annoying glitches, but at least it's reasonably stable..

Daedalus # 13. February 2006, 18:15

The favicon fix closes a bug I reported a while ago, very nice

Darn71 # 13. February 2006, 18:19

Well, I can confirm the favicon fix is working.
This weekly build thing is a great idea! My hd is going to be full of Opera backups, but wth...

elcid73 # 13. February 2006, 18:26

Should this be part of the "opera labs" page?

borg # 13. February 2006, 18:36

Opera Labs is a portal page to technology previews and betas from different Opera teams. This blog is meant to give a closer look into the daily life of the Desktop Team.

Blog entries may not be as polished as on labs.opera.com, and the weekly builds may have more rough edges than what we dare to publish to a larger audience

Kildor # 13. February 2006, 18:48

Why
Removed support for "javascript:" URLs in CSS.?

Junyor # 13. February 2006, 18:51

@MarkGillespie: Bug report?

@Kildor: Security.

WildEnte # 13. February 2006, 18:55

Good idea with weeklies!

I suggest that you set up some kind of bugtracker though - otherwise it's hard to disentangle what was fixed already and what not, if some people report bugs for TP2 and others for a weekly. This would (hopefully) also reduce the amount of bug reports on the same bug (simply add a "confirm bug" button to see how many people find it, to get an idea how important the bug is).

As usual: thumbs up opera team!

Darn71 # 13. February 2006, 19:17

Going to opera:config and entering more than 1 letter in the filter box crashes Opera... :/

Elephan7god # 13. February 2006, 19:25

is there a UserJS support in the new build? 'cause i can't find where i can specify the userJS folder...

Junyor # 13. February 2006, 19:27

@Darn71: Already mentioned on the previous page.

Kildor # 13. February 2006, 19:38

Not always, but often…
PS: Can send Inspectr log

Darn71 # 13. February 2006, 19:54

@Junyor: Oops. Blame it on exitement.

Bug: Go to posten.no. Create a search from the text box under "Spor sendingen din". Opera will crash whenever you try to use that search. It creates a POST search btw.

_Grey_ # 13. February 2006, 19:55

Well, at least I don't like the way autofocus is supposed to work in the Web Forms 2.0 spec ... I've already mailed to the mail list but it got under the shelves, it seems.

I think it's stupid to allow web authors to use multiple elements with that attribute. One should only respect the first and skip the others, imho.

I'm excited about weeklies, don't know what I should think of it, though. For the most people, though, this is definately a plus, I guess.

mgillespie # 13. February 2006, 20:01

I havn't raised a bug report, as the current bug tracker is so bad. Nobody outside Opera knows if anyone acutally reads them, or if they fall intoa giant bucket.

Opera need something like Bugzilla, where reporters can check progress, and devs can ask for fruther info. Without this, I feel bug reporting is a waste of time... :-(

yokey # 13. February 2006, 20:02

Good idea develop Opera browser
-------
opera crash often print preview
and freeze upload files to host Free etc.
http://rapidshare.de/
http://www.sendspace.com/

thank Desktop Team
I from user in thailand

_Grey_ # 13. February 2006, 20:26

Once the bug tracker is public, there's no way to go back to non-public.

I don't think it's wise to open the bug tracker at this stage of developement. If Opera gets a more significant marketshare, that would more likely be a benefit for the company and its browser(s).

You can't simply mix up essential parts of open source society with commercial closed-source projetcs and expect it to work. At this point of time, this would lead to major uncertainties in the browser world.

I agree, though, that there should at least be feedback like "duplicate bug" or "not a bug at all" or something else. But that's up to budget, I think.

Pondus # 13. February 2006, 20:30

Just curious: Will «Opera Image Control Status Bar Spoofing Weakness» found on Secunia.com be fixed before Opera 9 goes final?

hcastill # 13. February 2006, 20:32

I get an instant crash when rearrenging the order of the movies in the Netflix Queue. Filled bug-196341. It did not happen with last's weeks release.

MihLab # 13. February 2006, 20:38

Idea of weekly releases good.
At me a problem such: at closing a browser - process the Opera periodically is not unloaded from memory.
I use Win2003 Ser EE Sp1.

hcastill # 13. February 2006, 20:41

One other thing, Top 10 List appears to be fixed.

csant # 13. February 2006, 20:50

Pondus, the technical previews of Opera 9 are not vulnerable.

quiris # 13. February 2006, 21:06

Great suprise

It would be nice to publish with weekly changelog also fixed bug numbers, because some of a testers maintain lists of bug reports sent. The numbers would be very helpful to check what was fixed.

Pondus # 13. February 2006, 21:13

csant: OK, thanks. Maybe Secunia should be notified then? Or do they wait until Opera 9 is final?

csant # 13. February 2006, 21:34

Secunia does usually not consider products that are not in final stage for their advisories.

Michael83815 # 13. February 2006, 21:48

This is great for us testers. I'm a web developer and this gives me a chance to test the new rendering capabilities.

Thanks Opera

jmwatte # 13. February 2006, 21:48

Good idea...

Some things (I donn't know if anyone mentioned them.)
The Top10-thing-ie: used to be "the top 10 most used"...is now " 10 most recently used".
2. When closing down my computer... somehow Opera is blocking the shut-down proces(windows)
But I still like it..

porneL # 13. February 2006, 22:15

I've got scared when I saw vanilla config instead of mine. Fortunately weekly builds just use separate config directory on OS X. Unfortunately linking old one to new one doesn't work very well (mail is disabled).

Junyor # 13. February 2006, 22:37

@mgillespie: We use the BTS all day, every day. We'll contact you if we need more information about a bug report.

Sushubh # 13. February 2006, 23:12

dudes, you should consider fixing the 'top 10' bug soon... its the only thing that's making me go nuts in tp2.

Sushubh # 13. February 2006, 23:13

and after commenting maybe, the focus should be on the commented comment... i was thrown to the first page itself...

Sushubh # 13. February 2006, 23:24

another stupid request... rss feeds for comments on the blog?

elvis # 13. February 2006, 23:31

hmm, i saw your earlier comments about the reasoning for not making this a part of the opera labs site, but suddenly we have two disjointed but fundamentally overlapping parts of the opera site lying around... perhaps there should at least be links from one to the other?

example: my first instinct on hearing about weekly builds was "hmm, ok, newly annouced cutting edge opera stuff -- that'll be on the newly announced opera labs page then" <browse over there> "ummm... where is it?"

confusing.