prasad1979
Member
- Joined
- 29 Nov 2012
- Messages
- 370
- Reaction score
- 305
Opera Neon is refreshing take on browser! It brings surfing in the focus & keeps other distractions away. Needs adblock extension asap though.
- Thread starter Bapun
- Start date
- Replies: Replies 631
- Views: Views 166,100
rahul1117kumar
Member
- Joined
- 21 Jun 2013
- Messages
- 10,365
- Reaction score
- 11,058
Mozilla Reveals a New Logo Alongside Major Redesign
Mozilla has finally introduced a new logo, design, colour palette, font, imagery, and language architecture as a part of its new brand identity. The new Mozilla logo, the company says, 'reinforces that the Internet is at the heart of Mozilla'. This comes as a first such attempt made by Mozilla Foundation since its launch in 1998. Alongside, Mozilla has also released The Internet Health Report, which is an open source initiative by the company to explain what's happening to the health of Internet.
Last year in June, Mozilla set out to refresh its brand identity under a open source design project that crowdsourced ideas, and subsequently votes from the public on how it should redesign itself. The new logo is a modified version of the original logo where 'i' and 'l' have been redesigned to look more like Internet elements. The new Web font used in the logo is called 'Zilla', which is also free and open for use. "Zilla has a journalistic feel reinforcing our commitment to participate in conversations about key issues of Internet health," says Mozilla in a statement.
Apart from these, the colour palette has also been redefined to flow through different aspects of Mozilla's brand identity like logo and design. The language architecture includes copy lines on the right or below the core Mozilla messages or program, event, and team names that unifies Mozilla's activities and initiatives. The company has also made 'imagery' an important component of its brand identity. "Since imagery is an important reflection of the diversity and richness of the Internet, however, we've made it an important component of our system" says Mozilla in its statement. For imagery to work, Mozilla invites artists, designers, and technologists to contribute to an imagery collective, post that it will code curated GIFs, animations, and still images to flow into mozilla.org and other digital experiences.
Besides, Mozilla Foundation has also released its Internet Health report where it talks about what's happening with the health of Internet considering the aspects of decentralisation, digital inclusion, open innovation, privacy & security, and Web literacy. It has been compiled using different sources and reports the pattern of use of Internet across the globe. You can read the entire report on The Internet Health website.
Mozilla Reveals a New Logo Alongside Major Redesign | NDTV Gadgets360.com
Mozilla has finally introduced a new logo, design, colour palette, font, imagery, and language architecture as a part of its new brand identity. The new Mozilla logo, the company says, 'reinforces that the Internet is at the heart of Mozilla'. This comes as a first such attempt made by Mozilla Foundation since its launch in 1998. Alongside, Mozilla has also released The Internet Health Report, which is an open source initiative by the company to explain what's happening to the health of Internet.
Last year in June, Mozilla set out to refresh its brand identity under a open source design project that crowdsourced ideas, and subsequently votes from the public on how it should redesign itself. The new logo is a modified version of the original logo where 'i' and 'l' have been redesigned to look more like Internet elements. The new Web font used in the logo is called 'Zilla', which is also free and open for use. "Zilla has a journalistic feel reinforcing our commitment to participate in conversations about key issues of Internet health," says Mozilla in a statement.
Apart from these, the colour palette has also been redefined to flow through different aspects of Mozilla's brand identity like logo and design. The language architecture includes copy lines on the right or below the core Mozilla messages or program, event, and team names that unifies Mozilla's activities and initiatives. The company has also made 'imagery' an important component of its brand identity. "Since imagery is an important reflection of the diversity and richness of the Internet, however, we've made it an important component of our system" says Mozilla in its statement. For imagery to work, Mozilla invites artists, designers, and technologists to contribute to an imagery collective, post that it will code curated GIFs, animations, and still images to flow into mozilla.org and other digital experiences.
Besides, Mozilla Foundation has also released its Internet Health report where it talks about what's happening with the health of Internet considering the aspects of decentralisation, digital inclusion, open innovation, privacy & security, and Web literacy. It has been compiled using different sources and reports the pattern of use of Internet across the globe. You can read the entire report on The Internet Health website.
Mozilla Reveals a New Logo Alongside Major Redesign | NDTV Gadgets360.com
Chrome 56 rolling out to Mac, Windows, and Linux, full HTML5 by Default & ‘Not Secure’ label rollout
HTML5 by Default is now enabled for all users. Additionally, all sensitive HTTP sites will be marked as unsecure in the address bar.
Mostly benefiting the Mac, support for playing FLAC audio files is now available in Chrome 56.
Other features include the Web Bluetooth API that allows web apps on Android, Chrome OS, and Mac to communicate with nearby Bluetooth Low Energy devices.
Chrome 56 rolling out to Mac, Windows, and Linux, full HTML5 by Default & ‘Not Secure’ label rollout | 9to5Google
HTML5 by Default is now enabled for all users. Additionally, all sensitive HTTP sites will be marked as unsecure in the address bar.
Mostly benefiting the Mac, support for playing FLAC audio files is now available in Chrome 56.
Other features include the Web Bluetooth API that allows web apps on Android, Chrome OS, and Mac to communicate with nearby Bluetooth Low Energy devices.
Chrome 56 rolling out to Mac, Windows, and Linux, full HTML5 by Default & ‘Not Secure’ label rollout | 9to5Google
Firefox 51 released, becomes the first browser to support all new WebGL 2
New:
Added support for FLAC (Free Lossless Audio Codec) playback
Improved reliability of browser data sync
An even faster E10s! Tab Switching is better!
Added Georgian (ka) and Kabyle (kab) locales
A warning is displayed when a login page does not have a secure connection
Added support for WebGL 2, with advanced graphics rendering features like transform feedback, improved texturing capabilities, and a new sophisticated shading language
Firefox will save passwords even in forms that do not have “submit” events
Improved video performance for users without GPU acceleration for less CPU usage and a better full screen experience
Added a zoom button in the URL bar:
Displays percent above or below 100 percent when a user has changed the page zoom setting from the default
Lets users return to the default setting by clicking on the button
Users can view passwords in the save password prompt before saving them
Remove Belarusian (be) locale
fixed :
Various security fixes
changed :
Updated to NSS 3.28.1
Re-enabled E10s support for Russian (ru) locale
Use 2D graphics library (Skia) for content rendering on Linux
Firefox — Notes (51.0) — Mozilla
New:
Added support for FLAC (Free Lossless Audio Codec) playback
Improved reliability of browser data sync
An even faster E10s! Tab Switching is better!
Added Georgian (ka) and Kabyle (kab) locales
A warning is displayed when a login page does not have a secure connection
Added support for WebGL 2, with advanced graphics rendering features like transform feedback, improved texturing capabilities, and a new sophisticated shading language
Firefox will save passwords even in forms that do not have “submit” events
Improved video performance for users without GPU acceleration for less CPU usage and a better full screen experience
Added a zoom button in the URL bar:
Displays percent above or below 100 percent when a user has changed the page zoom setting from the default
Lets users return to the default setting by clicking on the button
Users can view passwords in the save password prompt before saving them
Remove Belarusian (be) locale
fixed :
Various security fixes
changed :
Updated to NSS 3.28.1
Re-enabled E10s support for Russian (ru) locale
Use 2D graphics library (Skia) for content rendering on Linux
Firefox — Notes (51.0) — Mozilla
rahul1117kumar
Member
- Joined
- 21 Jun 2013
- Messages
- 10,365
- Reaction score
- 11,058
Google makes page reloads work 28 percent faster for Chrome on smartphones
Google has announced enhancements to the way reloading pages works on Chrome for smartphones. Originally, the reload feature was designed to fix broken pages, and refresh the page to represent new content that has been added since the last time the page was loaded. The existing methods for reloading a page, worked better with fixing broken pages, and was less efficient at representing added content, especially on mobile phones.
The conventional methods for page reloads checks with the server if the cached resources are still usable, a process known as validation. The validation process results in hundreds of requests per page issued to dozens of domains. On low latency connections, over cellular networks, this can result in serious performance issues for users, and result in an overall bad experience for web surfing.
The outdated methods for reloading pages is a relic from the time broken pages were very common on the web, and web pages have improved a lot since that time. It is now unnecessary to address both the problems, of broken pages and additional content, at once. Google now has a simplified Chrome reload behavior where the main resources are verified, and the rest of the content continues to be loaded.
The latest version of Chrome reloads pages 28 percent faster. Facebook had contacted Google engineers over a worrying problem where Chrome users were reportedly sending validation requests at three times the rate of users of other browsers. After the update, Facebook has reported that there has been a 60 percent reduction in validation requests from Chrome.
Google makes page reloads work 28 percent faster for Chrome on smartphones Tech2 Mobile
Google has announced enhancements to the way reloading pages works on Chrome for smartphones. Originally, the reload feature was designed to fix broken pages, and refresh the page to represent new content that has been added since the last time the page was loaded. The existing methods for reloading a page, worked better with fixing broken pages, and was less efficient at representing added content, especially on mobile phones.
The conventional methods for page reloads checks with the server if the cached resources are still usable, a process known as validation. The validation process results in hundreds of requests per page issued to dozens of domains. On low latency connections, over cellular networks, this can result in serious performance issues for users, and result in an overall bad experience for web surfing.
The outdated methods for reloading pages is a relic from the time broken pages were very common on the web, and web pages have improved a lot since that time. It is now unnecessary to address both the problems, of broken pages and additional content, at once. Google now has a simplified Chrome reload behavior where the main resources are verified, and the rest of the content continues to be loaded.
The latest version of Chrome reloads pages 28 percent faster. Facebook had contacted Google engineers over a worrying problem where Chrome users were reportedly sending validation requests at three times the rate of users of other browsers. After the update, Facebook has reported that there has been a 60 percent reduction in validation requests from Chrome.
Google makes page reloads work 28 percent faster for Chrome on smartphones Tech2 Mobile
rahul1117kumar
Member
- Joined
- 21 Jun 2013
- Messages
- 10,365
- Reaction score
- 11,058
Google Chrome for iOS Finally Goes Open Source
Google has announced that after years of keeping Chrome for iOS separate from its Chromium project, it is now open-sourcing the browser on Apple's mobile platform. Despite the "additional complexity" associated with the platform, the company says that its team spent a lot of time over the past several years to make the necessary changes required to upstream the code for Chrome on iOS into Chromium.
If you are wondering why Chrome for iOS was kept separate from the Chromium project even though Android version joined Chromium back in 2015, this is because the iOS version of the browser is built on top of the WebKit rendering engine instead of Google's Blink engine. Due to the constraints associated with iOS, all browsers must be built on top of WebKit rendering engine, Google reminded readers in its blog post.
"For Chromium, this means supporting both WebKit as well as Blink, Chrome's rendering engine for other platforms. That created some extra complexities which we wanted to avoid placing in the Chromium code base," it added.
The upstreaming for the code has now been completed and developers can now compile the iOS version of Chromium just like they do for other platforms. "Development speed is also faster now that all of the tests for Chrome for iOS are available to the entire Chromium community and automatically run any time that code is checked in," the company said.
Google recently started rolling out Chrome 56 for Windows, Mac, and Linux. The latest version of the desktop browser notably flags certain HTTP websites as unsafe in the address bar and also puts HTML5 as default over Flash for all users.
Google Chrome for iOS Finally Goes Open Source | NDTV Gadgets360.com
Google has announced that after years of keeping Chrome for iOS separate from its Chromium project, it is now open-sourcing the browser on Apple's mobile platform. Despite the "additional complexity" associated with the platform, the company says that its team spent a lot of time over the past several years to make the necessary changes required to upstream the code for Chrome on iOS into Chromium.
If you are wondering why Chrome for iOS was kept separate from the Chromium project even though Android version joined Chromium back in 2015, this is because the iOS version of the browser is built on top of the WebKit rendering engine instead of Google's Blink engine. Due to the constraints associated with iOS, all browsers must be built on top of WebKit rendering engine, Google reminded readers in its blog post.
"For Chromium, this means supporting both WebKit as well as Blink, Chrome's rendering engine for other platforms. That created some extra complexities which we wanted to avoid placing in the Chromium code base," it added.
The upstreaming for the code has now been completed and developers can now compile the iOS version of Chromium just like they do for other platforms. "Development speed is also faster now that all of the tests for Chrome for iOS are available to the entire Chromium community and automatically run any time that code is checked in," the company said.
Google recently started rolling out Chrome 56 for Windows, Mac, and Linux. The latest version of the desktop browser notably flags certain HTTP websites as unsafe in the address bar and also puts HTML5 as default over Flash for all users.
Google Chrome for iOS Finally Goes Open Source | NDTV Gadgets360.com
Gmail no longer supporting Chrome Browser version 53 and below
Starting February 8, 2017, we will show a banner at the top of the Gmail interface for users who are still on Google Chrome Browser v53 and below to encourage upgrading to the latest version of Chrome, currently on version 55. Chrome Browser v55 contains several important security updates.
Gmail users that are still on Windows XP and Windows Vista are the most likely to be affected, because v49 was the last released version which supported those operating systems. As previously announced in April 2015 and November 2015, these systems are no longer maintained by Microsoft, and we strongly encourage you to migrate to more secure and supported systems.
What happens if users continue to use Chrome Browser v53 and below?
If you continue to use older versions of Chrome Browser now that support has ended, Gmail will be more vulnerable to security risks and users will not have access to new features and bugfixes.
Gmail will continue to function on Chrome Browser v53 and below through the end of the year. Users who remain on Chrome v53 and below could be redirected to the basic HTML version of Gmail as early as Dec 2017.
Recommendation
If you manage Chrome Browser for your users, we strongly encourage you to update users to the latest version of Chrome. Depending on what operating system your users are on, you may need to migrate them to a supported system to get the latest version and features.
Please note: Google does not typically announce when we discontinue support for older versions of Chrome browser because of our current supported browser policy, which states that only the most recent version of Chrome is supported. This announcement was made given the expected impact on Windows XP and Windows Vista users and known security risks.
G Suite Update Alerts: Gmail no longer supporting Chrome Browser version 53 and below
Starting February 8, 2017, we will show a banner at the top of the Gmail interface for users who are still on Google Chrome Browser v53 and below to encourage upgrading to the latest version of Chrome, currently on version 55. Chrome Browser v55 contains several important security updates.
Gmail users that are still on Windows XP and Windows Vista are the most likely to be affected, because v49 was the last released version which supported those operating systems. As previously announced in April 2015 and November 2015, these systems are no longer maintained by Microsoft, and we strongly encourage you to migrate to more secure and supported systems.
What happens if users continue to use Chrome Browser v53 and below?
If you continue to use older versions of Chrome Browser now that support has ended, Gmail will be more vulnerable to security risks and users will not have access to new features and bugfixes.
Gmail will continue to function on Chrome Browser v53 and below through the end of the year. Users who remain on Chrome v53 and below could be redirected to the basic HTML version of Gmail as early as Dec 2017.
Recommendation
If you manage Chrome Browser for your users, we strongly encourage you to update users to the latest version of Chrome. Depending on what operating system your users are on, you may need to migrate them to a supported system to get the latest version and features.
Please note: Google does not typically announce when we discontinue support for older versions of Chrome browser because of our current supported browser policy, which states that only the most recent version of Chrome is supported. This announcement was made given the expected impact on Windows XP and Windows Vista users and known security risks.
G Suite Update Alerts: Gmail no longer supporting Chrome Browser version 53 and below
Similar threads
