Straight from the build machine..
By Johan Borg. Friday, 10. November 2006, 16:27:04
Another weekly for you, smoking hot from the build servers, even our testers haven't played much with these before you, so be nice to them!
What you will see:
Fraud protection is not enabled by default anymore. We basically had to turn it on by default in the first weeklies to make sure we got as much feedback as possible in the limited time we had.
However, it's a new feature and we think users may need some time to get used to this idea, so we've made it an opt-in feature for now. Opera is about giving users the choice, after all.
Technically, there's a difference in how we transmit the data to the site check server. We now use https when we send information about an https server, to ensure that the trust information is at least as reliable as the original content. We still prefer to use http most of the time, since we're not very comfortable with sending home information that our users can't easily inspect.
Other changes:
We've fixed a number of bugs since last week, including the super-annoying gzip cache bug. NOTE: You may need to empty your cache before everything goes back to normal.
What's going on:
The desktop team was represented in the first Opera Backstage Russia event, in Ivanovo last week.
Next week we'll also participate in Webmaster World in Las Vegas. Be sure to drop by the Opera booth if you're there!
Yesterday, W3C released the first public working draft of the Widgets 1.0 specification, largely based on the current Opera implementation.
Changes since last weekly
Windows MSI
Windows Classic
Macintosh
Unix
What you will see:
Fraud protection is not enabled by default anymore. We basically had to turn it on by default in the first weeklies to make sure we got as much feedback as possible in the limited time we had.
However, it's a new feature and we think users may need some time to get used to this idea, so we've made it an opt-in feature for now. Opera is about giving users the choice, after all.
Technically, there's a difference in how we transmit the data to the site check server. We now use https when we send information about an https server, to ensure that the trust information is at least as reliable as the original content. We still prefer to use http most of the time, since we're not very comfortable with sending home information that our users can't easily inspect.
Other changes:
We've fixed a number of bugs since last week, including the super-annoying gzip cache bug. NOTE: You may need to empty your cache before everything goes back to normal.
What's going on:
The desktop team was represented in the first Opera Backstage Russia event, in Ivanovo last week.
Next week we'll also participate in Webmaster World in Las Vegas. Be sure to drop by the Opera booth if you're there!
Yesterday, W3C released the first public working draft of the Widgets 1.0 specification, largely based on the current Opera implementation.
Changes since last weekly
- Fixed bug where "Go to URL" feature deselects last one or two characters of a URL
- Fixed bug where newsfeed count did not updated in Mail panel status bar
- Fixed bug where cnn.com didn't always finish loading
- Fixed bug where accesskeys didn't work right on frame pages
- Fixed bug where Gzipped pages was not decoded when loaded from cache
- Added preference to disable trust button in address bar opera:config#SecurityPrefs|EnableTrustButton
- Fixed Finnish translation
Windows MSI
Windows Classic
Macintosh
Unix
WIDGETIZE
1 2 3 4 5 Next »
remcolanting # 10. November 2006, 16:51
kyleabaker # 10. November 2006, 16:52
neoscorp # 10. November 2006, 16:54
HydanSeeker # 10. November 2006, 16:54
(Too busy downloading & playing with this build before this post appeared.) Thanks for the heads up, jonspencerbx!
THANK YOU for making fraud protection disabled by default!
THANK YOU for gzip fix
THANK YOU for all your other hard work!
SpyMan # 10. November 2006, 16:57
Eddie_Lopez # 10. November 2006, 16:59
What's the general consensus on this Opera Community?
profiT # 10. November 2006, 17:03
I don't get it. Then what's point to make this protection? If casual users won't be bothered to enable it?
serious # 10. November 2006, 17:03
n1
alxtec # 10. November 2006, 17:04
dieburnbot # 10. November 2006, 17:04
Tracio # 10. November 2006, 17:04
Shouldn't it read opera:config#SecurityPrefs|EnableTrustButton?.
Trust rating toggles the auto check...
MossMan # 10. November 2006, 17:05
CharleneFerrara # 10. November 2006, 17:06
kyleabaker # 10. November 2006, 17:08
Appears to be fixed to me
Twilo # 10. November 2006, 17:10
remcolanting # 10. November 2006, 17:10
It would make sense that there will be an option when installing Opera in the final release.
SpyMan # 10. November 2006, 17:11
Thanks, I'll give this build a try, then.
kyleabaker # 10. November 2006, 17:12
I made this same comment earlier in the irc
FataL # 10. November 2006, 17:12
Headsick # 10. November 2006, 17:12
Thx for the new build and thx for the fixes of some bugs (like the youtube.com-bug).
Good work men.
Greetz, Headsick
cielkisu # 10. November 2006, 17:13
Junyor # 10. November 2006, 17:17
@Tracio: Yep, fixed.
@dieburnbot: Fixed
Eddie_Lopez # 10. November 2006, 17:19
I'd be interested in the process of how Opera determines what is turned on, what is hidden, what priority things get.
I'm reminded of the mouse gesture indicator:
I've always like that indicator, but I don't think Opera uses it anywhere else in the UI. While I agree that you definately don't want a dialogs like that popping up 10 times in the first minute of usage, I do like the way that introduces a feature and only "bothers" the user once.
Maybe something like that could be done here?
FataL # 10. November 2006, 17:23
Originally posted by Junyor:
Junyor, and why you moved away?cafesote # 10. November 2006, 17:27
Great job dev. Opera!
SalocinHB # 10. November 2006, 17:29
Finally, thank you!
Junyor # 10. November 2006, 17:30
@FataL: First impressions are important. Installing should be as easy as possible and users should not be assaulted with dialogs the first time they run Opera.
hurtig # 10. November 2006, 17:36
Jpg-pictures, which still have remains of exif-data, are not indicated basically in Opera. An old problem in Opera 9.
I hope this bug will be fixed somtime.
remcolanting # 10. November 2006, 17:36
In that case turning it on by default and putting a link of some sorts to disable it on the fraud warning page would be the easiest. Sorta like the mouse guestures are handled now
OperaBuddy # 10. November 2006, 17:42
"Fixed bug where cnn.com didn't always finish loading"
cnn.com still does not finish loading...us edition, "hanging" problem still exist.
DataKeeper # 10. November 2006, 17:42
http://
still get 100% CPU
but
ftp:// work fine "Error! Could not locate remote server"
non-troppo # 10. November 2006, 17:43
EDIT: yes a known bug: http://my.opera.com/community/forums/topic.dml?id=165307
HydanSeeker # 10. November 2006, 17:52
My apologies! I hate spam, and I didn't think my post would have been construed as spam! The post was written in good faith. Some users said the previous build killed their system. Many posts in the past point to third-party solutions, and I thought the software was worth a mention (not only for Opera weeklies but any other beta software being tested). I have absolutely no association with the product other than using it (like Opera).
I am well aware of installing Opera in separate directories (a feature I love and use often!), but my post outlined additional benefits not available with a separate directory install, which would prevent/resolve other issues posted previously.
non-troppo # 10. November 2006, 17:56
As I see it, in the default install, the trust button is enabled even though site check is disabled. Thus a user can easily click and enable that feature. Opera's UI alerts the user to the possibility. Even so, naive users may ignore the icon - there is not even a tooltip to suggest what it does.
Thus, on the first run page after installing opera - it maybe worthwhile prominantly featuring a box with information suggesting users turn it on?
kyleabaker # 10. November 2006, 18:00
I hear that. Nothing like a clean install then straight to surfing, but it would make sense to launch a secondary page to inform new users. This secondary page could easily be closed and/or kept open while the user continues to surf the web.
g4qb # 10. November 2006, 18:01
double clicking on ULP, etc.
still dead.
love the highlighting colours,
yellow & green
more visible.
try this page
odd rendering by opera???
http://www.ac3.edu.au/edu/support.html
try to get to the email address; the drop down menus are activated.
also check this
1. go to Help About Opera
2. search 4 ion - Ctrl-F "ion", F3
3. note that 1st instance is highlighted but not selected.
this has been going on since 9.02.
andresruiz # 10. November 2006, 18:02
Looks great, I'm busy finishing a webpage for tomorrow morning but after that I'll test the new build.
I do like things that you solve on every build, but I don't like the speed, maybe we'll be testing 9.1 final next year.
Bye
MisterE # 10. November 2006, 18:05
Regarding the fraud protection: I have it disabled (so I can manually check when needed). After you manually check, the icon should change from the default question mark. After all, the site is now checked and should display the same icon as a verified site (a small i IIRC).
Twilo # 10. November 2006, 18:15
The page you are trying to open has been blacklisted as fraudulent. It will likely attempt to trick you into sharing personal or financial information. We strongly discourage visiting this page. Learn more about Opera's fraud protection.
CaseyJ # 10. November 2006, 18:20
gregbzh # 10. November 2006, 18:31
dantesoft # 10. November 2006, 18:33
Junyor # 10. November 2006, 18:58
@remcolanting: Users can easily enable it by clicking the "?" in the address bar.
NeroW # 10. November 2006, 19:19
With this build Opera has come closer to rendering it
properly, but still no cigar.
It is no good recommending Opera to others if it can't
render a 'mainstream' site like this -- and there are
several others too.
As I have written before, the last build to get this
right was 8432 - so it should be possible to fix it.
gorsov # 10. November 2006, 19:22
Again, regarding the mailto handling bug (230879):
I suggest temporarily change the way Windows Explorer is supposed to open mailto urls with Opera -- mailto parameters string currently can be passed to opera.exe as a command line parameter (not via DDE).
remcolanting # 10. November 2006, 19:23
You can also say exactly the opposite, that users can easily disable it there.
Having the icon there so users can check manually if it's disabled is a good thing, but it also implies that fraud protection is enabled. It should be made clear that it's off by means of a different icon, like a "M" for manual.
If that's the case, it doesn't really matter if it's on or off by default because it's very clear to the user what the setting is. Clicking it will enable the user to view and change it, just as someone would expect.
predatorian # 10. November 2006, 19:27
MisterE # 10. November 2006, 19:35
Because of the way the check is made ("calling home"), I think it's best left disabled by default so that Opera will not be called spyware.
klingoncowboy4 # 10. November 2006, 19:47
Oh and can someone tell me why I didn't get an update about this build through the RSS feed?
Edit: It just came in
remcolanting # 10. November 2006, 20:02
The problem is that you want to protect the novice user as well as possible while allowing power users to do everything they want. Opera already made the choice that the additional protection outweighs the 'calling home' by adding this feature.
The question that remains is, do you want novice users to enable it or power users to disable it? The latter would make more sense because novice users don't know as much as power users about Opera and security issues.
I believe that users that don't trust Opera to handle the fraud protection data with care shouldn't use Opera at all. You never know what's hidden inside the program. With all the off-site ads nowadays, it's really easy to put in an extra request while loading a page.
The conclusion is pretty simple: if you want to be safe, stay off the internet! Ofcourse we don't want that, so the focus should be to make everything absolutely clear for the user. Altering the icon to show it's disabled is something that can be easily done but is very effective in making things clear.