Extension improvements, updates to Core and some other nice fixes

Readers' comments

Comments left by My Opera members under the original post: the first 50, as archived.

• Ria Nav6. December 2010, 12:35

  Finally. Thank you testing now!

• sebt6. December 2010, 12:36

  

• bachokocho6. December 2010, 12:37

  Thank you, thank you, thank you
  Clean install

• Arguggi6. December 2010, 12:38

  Was waiting for this
  
  Testing

• BS-Harou6. December 2010, 12:39

  All in all we think this is a pretty great snapshot. Let us know if you agree!

  
  Definitely! Mainly the HTML5 forms, I've been waiting for this for so long and it's finally here

• Frans6. December 2010, 12:39

  Ooh, very nice. I've been waiting for updated Webforms.

• Justas6. December 2010, 12:40

  Thanks, been refreshing your blog for a while

• Ruarí Ødegaard6. December 2010, 12:41

  @BS-Harou: I'm disappointed that you didn't make the first post as I tweeted you as I made it live.

• Topi6. December 2010, 12:42

  yey
  Still no fix for gesture detection?
  
  
  edit:
  
  THIS BUILD CRASHES A LOT!!!
  
  (about 10 reports sent by now...)

• Jasper Thai6. December 2010, 12:42

  Wow, new week and new release

• Gregorius6. December 2010, 12:46

  last.fm js is not working correctly.
  I can't dropdown the list to like song
  

• sebt6. December 2010, 12:47

  DSK-320509, DSK-320512, DSK-320515 not fixed.
  
  (Ctrl+)Shift+Enter at address bar still broken.
  
  Single key shortcuts 1 and 2 not working correctly with tab stacks.
  
  "Open new tab next to active" broken when stacks are in use.
  
  Gestures are still not working sometimes.
  
  Seb

• Daniel Hendrycks6. December 2010, 12:48

  

• Jan Mikula6. December 2010, 12:49

  When I use button for open new tab in Tab bar Opera crash.

• SF816. December 2010, 12:50

  Ups, none of my 'most hated bugs'* list has been addressed, but thanks anyway. Opera 11 beta is still great.
  
  * 1) Restored tabs don't remember last restored tab size.
  2) That redraw problem with the border of restored tabs.

• BS-Harou6. December 2010, 12:52

  Originally posted by ruario:

  @BS-Harou: I'm disappointed that you didn't make the first post as I tweeted you as I made it live.

  
  That would be too much happiness for one day + I'm used to read always whole post and changelog before posting a comment

• sirnh16. December 2010, 12:52

  A little error in the HTML 5 'type=number'. If (in the demo) you enter a shoesize of 555 you get this:
  
  (Note the %2 in the error? I guess that should be a number 18 or 25 or something

• Floriano Ferreira6. December 2010, 12:55

  Speed dial is still ugly as hell (thumbnails streched) as the previous build.

• Crabman6. December 2010, 12:56

  Oh no, the "Show Gesture UI"-option is gone and the Mouse Gesture Hints are back. Apart from that nice changelog.
  
  A small nitpick: I don't like the animation when the second tab in a group with two tabs is closed and the group "disappears". The remaining tab animates like when a new tab is opened but imo it shouldn't as it's not really new. The second tab should just disappear. Looks a bit messy right now.

• Ruarí Ødegaard6. December 2010, 12:56

  Originally posted by BS-Harou:

  I'm used to read always whole post and changelog before posting a comment

  Ah, in that case do not change this admirable behaviour!

• Gereford6. December 2010, 12:58

  Thx. Testing.

• Nico6. December 2010, 13:00

  Thank you for the Snapshot, I've been waiting for this .
  
  By the way: Are there any plans to support Vista's/Seven's default explorer for saving files before Opera 11 goes final? The current explorer window looks really old and lacks some basic functions, like the improved breadcrumb bar.
  
  
  Thanks again for a new Build!

• Rijk6. December 2010, 13:02

  Originally posted by sirnh1:

  A little error in the HTML 5 'type=number'.

  Yes, saw this yesterday when working on the Dutch translation
  

• Asires6. December 2010, 13:03

  Autooptimization of stacks (compress inactive) is completely not working now! Usability is slowing down. For what? Very bad idea. Better, if autooptimization of other stacks remains when open some stack by double clicking (but not by Expand button). It's best and only way.
  
  Also, autostacking.. I mean, all unstacked tabs create it. Useless. I don't need to see stacks most of the time, when open 5 sites with 2-3 tabs each. Now stacks is everywhere, eats space (not add it!) and interfere in simple tab management. Keep it simple, please!
  
  New tabs opened from stacked page remains in own stack is good thing of course. No probs here.

• Stanley6. December 2010, 13:04

  i use the last stable version, I don't know if it works in this one, but there is a new version of grooveshark and it's not working for opera at all.

• micsk6. December 2010, 13:05

  I always wonder whether the bugs/suggestions mentioned in the blog comments are analysed - or is it better to post in forums/bug tracker?
  
  Furthermore I appreciate it that you fixed some crashes - crashing and memory usage are two things which dramatically increased since Opera 10.

• BS-Harou6. December 2010, 13:06

  It's still not possible to send a form with "enter key" when focus is in <input type="number">

• Topi6. December 2010, 13:07

  Mod edit: Please do not comment on builds you are not going to test.
  
  
  Edit for mods: I did test this build and my conclusion was:
  
  

  Originally posted by mikyjr:

  When I use button for open new tab in Tab bar Opera crash.

  
  
  Same here. This build is crashing like a h*ll. Have to roll back.
  
  
  Edit for mods: Pleace moderators could tell me how I'm "not going to test" this build if I had it installed already? It's just impossible to use it as my primary browser BUT that doesn't mean I don't use/test it at all. I have multiple installations of all browsers.
  
  If you don't like the fact that this build crashes a lot, just say it.

• BS-Harou6. December 2010, 13:09

  And it's still not possible to clear value of <input type="datetime"> .. when I use this in javascript:
  var dt = document.querySelector("input[type=datetime]");
  dt.value = dt.defaultValue;
  then nothing happens

• hurug6. December 2010, 13:09

  OK same here

• Obese Maurice6. December 2010, 13:09

  There is no option to disable Gesture UI. If you renamed previous option to "Showed Gesture Info", it doesn't work anymore. UI is always ON.
  
  And mouse gestures are still broken.

• ColKilkenny6. December 2010, 13:10

  Any way to make Opera not to open new tabs in same tab group? I'd like to manually stack the tabs, no need for automatical stacks.
  
  And we need a way to disable the Gesture UI.

• Publisher6. December 2010, 13:10

  I can't confirm on windows 7 pro x86

• porneL6. December 2010, 13:17

  Gaps between tabs got huge, and they're not getting smaller when there's lots of tabs open.
  
  http://imgur.com/619MB.png
  
  

• Arguggi6. December 2010, 13:18

  Originally posted by ColKilkenny:

  Any way to make Opera not to open new tabs in same tab group? I'd like to manually stack the tabs, no need for automatical stacks.

  
  
  +1, tabs already in a stack should open background tabs in the stack, tabs that aren't in a stack shouldn't create a new stack when I open a background tab.

• Gousti Fruit6. December 2010, 13:19

  Originally posted by ColKilkenny:

  Any way to make Opera not to open new tabs in same tab group? I'd like to manually stack the tabs, no need for automatical stacks.

  
  I find it to be a very neat feature, whenever I open new tabs from an existing one, I want them to stay grouped, so the way it works now is perfect. I don't see how someone could want another way of working, but as always with Opera, they will eventually come with an option to set it the way you want.
  
  Concerning the Mouse Gestures feature, maybe I'm getting used to the way it is now, because I have lot less problems than a few builds ago; but I also changed the value to "30", that may have its importance.

• Gousti Fruit6. December 2010, 13:20

  Next improvement for the stacked tabs could be to reopen close tabs in the stack they were in, but it could be something very complex to manage !

• Obese Maurice6. December 2010, 13:22

  Originally posted by Arguggi:

  +1, tabs already in a stack should open background tabs in the stack, tabs that aren't in a stack shouldn't create a new stack when I open a background tab.

  
  
  +1 Very strange. I want automatic stacking by domain.

• Jasper Thai6. December 2010, 13:22

  Crash (

• Alexx Izumoff6. December 2010, 13:23

  Thx for Great build! Some regressions:
  1) turning off opera:config "show gesture info" - still shows Gesture Circle with advices on Mouse Gestures. Even after Save-Restart opera.
  2) Tab Stacking if I open A link from current page - it goes into stack (two pages - current + new one). But if I'm On current page in Stack and Opens New tab (Gesture Mouse Down or Ctrl+t) - My Stack is splitted into TWO stacks with "Speed Dial" pages between them. Its strange ^)
  
  

• Ike Devolder6. December 2010, 13:26

  I like the Automatic stacking, but maybe we could have some shortcut for closing the stack ?

• sebt6. December 2010, 13:31

  Originally posted by ObeseMaurice:

  There is no option to disable Gesture UI. If you renamed previous option to "Showed Gesture Info", it doesn't work anymore. UI is always ON.
  
  And mouse gestures are still broken.

  
  Confirmed both problems. It seems that gestures just don't work half the time, I have to swipe L 3+ times now to close a page.
  
  Seb

• Michael6. December 2010, 13:31

  It would have been nice of the multiple-key shortcut functionality had been restored with this release.

• Matheus6. December 2010, 13:33

  Originally posted by SF81:

  Ups, none of my 'most hated bugs'* list has been addressed, but thanks anyway. Opera 11 beta is still great.
  
  * 1) Restored tabs don't remember last restored tab size.
  2) That redraw problem with the border of restored tabs.

  
  
  Same for me!

• Avola6. December 2010, 13:35

  In the last couple of builds the 'activate next tab when closing tab' option doesn't always work; sometimes it goes to the previous tab, or last active one instead. And in the automatically generated tab stacks, closing tabs always brings me back to the first tab in the stack. Pretty annoying..

• g2spot6. December 2010, 13:38

  Originally posted by freerider:

  i use the last stable version, I don't know if it works in this one, but there is a new version of grooveshark and it's not working for opera at all.

  
  For me it works if I disable the NoAds extension on that site.
  
  Regression:
  1) The error messages that can pop up on form validations opens on primary screen when Opera is on secondary screen. Worked correctly in b1111.
  2) The active tab changes location (moves to the left/bottom) inside the stack when collapsing and expanding the stack.
  3) The tab closest to the little arrow to expand/collapse the stack (leftmost/topmost) is smaller than the other tabs.
  Edit: 4) When opening a tab with "new tab" with the option "open next to active tab" and the active tab is in the middle of a stack, the new tab splits the stack into two.
  
  /g..

• Tore Olavson Buarøy6. December 2010, 13:43

  Now my Opera is starting without crashing. Now I can start over. Thank you, Opera Desktop Team!

• joelson00076. December 2010, 13:44

  BUG:two keys keyboard shortcut not working here this build Opera 11.00 Build 1128
  BUG:two keys keyboard shortcut not working here this build
  
  example keyboard shortcut >> b, a =not working
  example keyboard shotcut >> a = working
  

• QuHno6. December 2010, 13:47

  Tested my JS buttons and they work again. THX for fixing CORE-33876
  
  ... but DSK-319557 freezes this build too

• Morphdreamer6. December 2010, 13:48

  Awesome changelog, especially HTML5 forms updates
  
  Just one question - in beta expanding tab stack caused other stacks to collapse. Is there a way to enable this behavior in this snapshot?