Google has just released their Chrome 63 beta, after only one week of Chrome 62 having been launched in its stable version. Chrome 63 beta brings some changes that are useful to developers, but there are also a few changes regarding UI.
Developers will have dynamic module imports, a Device Memory API, and async iterators and generators.
Permission Requests, Chrome Home and Flags Page – New Changes
Looking at the UI changes, users will see less permission requests, so that the whole user experience stop from being distracting. The permission prompts will be reduced to 50%, but they will appear as dialogs that users can no longer ignore, and they must either accept or deny them, instead of ignoring them. Google suggested that developers should ask for permissions at the right time, so that users can grant those permissions to the sites that provide context.
There are other changes to be found in Chrome 63: Chrome Home is the new name for the bottom address bar, and it has rounded corners and new elements. The UI changes to Chrome Home were released in the previous Chrome build (62), but they weren’t enabled by default – just as Chrome Home isn’t either.
If you get Chrome 63, you will also see a message at the top of the menu, opening a pop-up message that describes the new features that have been added. You can also toggle to disable the message.
Even the chrome://flags page looks different, the Android version shows us larger targets for us to touch, and a search bar.
9to5Google mentions a new option to Chrome 63 that will be available: the ability to mute all audio from a site, working on individual sites. It will be accessible in the site settings, and users can either ‘Allow’ or ‘Block’ it from the permissions panel.
The stable version of Chrome 63 will be available in a few weeks.
