![]() 60 release, so we're missing a bulk of fixes:ĭNA-75464 Crash at base::Time::Explode(bool, base::Time::Exploded*)ĭNA-76582 New tab button hover state should look like inactive hovered tabĭNA-76909 Crash at views::BridgedNativeWidgetImpl::SetParent(NSView*)ĭNA-76938 Rate Opera – black text on gray backgroundĭNA-76963 Crashes with easy setup panelĭNA-77341 Extensions actions should be hidden in overflow menu when they occupy more than 1/3 of toolbar size.ĭNA-77346 Use bigger tiles after update to R3 for some usersĭNA-77347 Tab preview stuck when dragging tabĭNA-77350 The location services disable button brings up an empty popupĭNA-77361 Crash at opera::PageView::is_locked()ĭNA-77390 Previous wallpaper color blinks when focusing tab with start pageĭNA-77403 Tailor font size for fallback tilesĭNA-77545 Opera crashes when trying to create snap Instead, Opera Beta is stuck at the "old". Who's using Opera Beta is still affected by issues solved in Opera Stable: they should make "v.70" available also in the beta channel (I don't care if they call it. And that's simply weird: a beta is supposed to "be promoted" to Stable once that it's stable enough. ![]() I'm not complaining about the version number, the problem is that latest beta is not updated as latest stable. Salvuccino last edited by problem is that they don't share the same code. In any case, I'll likely switch to stable, because if beta is not always ahead of stable (=being able to test/use recent fixes), it makes no sense to use it. Now you are welcome to laugh with everybody else, usual fanbois of this blog excluded of course. The situation is the following though lol, stable left out the oven so early (like always) and because it is so broken it acts like the beta, so stable and beta are updated at the same time to 3255.37, 3255.56, 3255.57, 3255.59, 3255.60, now to 3255.70 and will get probably at least 5 updates more. At this point both stable and beta should have the same build number, stable does not need any further updates by definition and the next stream with the new "locked" developement features goes to the other stream (beta) to get its bugs fixed, in this case 61. In this case -as in almost every other case in the past- if you check the changelogs, "theoretically" Opera beta was ready to be promoted at version 3255.27 in April, 9th. "In a serious company that respects its own words/statements the beta reaches a point where there are no bugs left to fix so the last version of it is being promoted to stable. There's an interesting thread about it on Opera blogs and I'm not alone : For example, the Ars journal box, top stories pager, and story view filter don't work properly in Opera Mini beta 5.Salvuccino last edited a software engineer, I always prefer to have a beta version ahead of stable in terms of fixes/updates/features. The downside of Opera Mini's client/server model is that complex JavaScript doesn't always behave as expected. Opera Mini's backend infrastructure uses the HTML rendering engine from Opera's desktop browser, which means that Opera Mini can reproduce complex webpages with relatively high accuracy. These features are also available in the latest Opera Mobile beta, which we reviewed last year. It automatically wraps blocks of text so that it will fit the width of the screen, effectively eliminating the need for horizontal scrolling. In that rewrite, Opera aimed to deliver a more desktop-like browsing experience by displaying the full page and allowing users to zoom in and scroll through content. The Opera Mini codebase was rewritten almost entirely for version 4, which was released last year. It's worth noting that this rendering mechanism is also used to facilitate "Turbo Mode" in Opera Mobile. In addition to significantly reducing the amount of work that has to be done on the user's mobile device, this approach also boosts page loading speed. ![]() In order to reduce bandwidth consumption and computational overhead, Opera Mini relays all page requests through Opera's backend server infrastructure which will load and prerender page content and then compress it before transmitting it to the user. Opera Mini is Opera's lightweight MIDP browser for J2ME-enabled feature phones and other devices that aren't capable of running Opera Mobile. With swift page rendering and top-notch usability, it's guaranteed to turn heads. It offers an outstanding new user interface that is a significant improvement over previous versions of Opera Mini and even outshines the most recent builds of Opera Mobile. Opera Mini got a boost this week with the launch of the first Opera Mini 5 beta release.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |