177 captures
29 Apr 2017 - 25 Apr 2026
Jul
AUG
Sep
01
2017
2018
2019
success
fail
About this capture
COLLECTED BY
Collection:
Twitter Outlinks
This is a Collection of URLs (and Outlinked URLs) extracted from a random feed of 1% of all Tweets.
TIMESTAMPS
The Wayback Machine - https://web.archive.org/web/20180801024411/https://blog.chromium.org/2015/06/
Chromium Blog
News and developments from the open source browser project
File System Provider API for easier file management
Thursday, June 11, 2015
On Chrome OS, users should be able to work with files in the cloud as easily as they work with local files.
Today, users often have their files spread all over the cloud -- with documents in one place, their photos in another, and videos somewhere else. Working across all of those systems can be a challenge, which is where the
File System Provider API
in Chrome OS can help. With the File System Provider API, users who install your Chrome App can have your Cloud service seamlessly integrated into the Chrome OS Files app. Working with multiple storage backends becomes as easy as dragging and dropping files locally.
As usual, users can install your Chrome app or extension from the Chrome Web Store. Or, they can add new services directly from the Files app. The new file system will then appear directly in the left navigation column. Users can browse this file system anywhere the Files app is shown, including Save as and Open dialogs.
Your extension just needs to call chrome.fileSystemProvider.mount and respond to the listed events. Developers have already created some great apps, including the
Box.com official client
, an
SMB client
, and even a way to browse
TED talks
locally. Check out the
documentation
or join the
mailing list
to stay informed about announcements and API changes.
Posted by Tomasz Mikolajewski, Filesystem Fiend
Chrome 44 Beta: Improvements to Notifications API and promoted add to homescreen
Tuesday, June 2, 2015
The newest Chrome
Beta
channel release includes new ES6 features and a number of updates to existing APIs. Unless otherwise noted, changes described below apply to Chrome for Android, Windows, Mac, Linux and Chrome OS.
Improved notification capabilities
Chrome 42 allowed users to opt in to receive
push notifications
from sites even after the page is closed. Sites may now use
getNotifications
to observe which of their notifications are still being displayed, and
Notification.data
to store a payload with a notification so they can determine which notification was clicked.
Promoted add to homescreen improvements
Since Chrome 42, users who frequently visited a high-quality web app on Android saw a banner allowing them to
add the site to their home screen in one tap
. In this release Chrome fires a
cancellable
beforeinstallprompt
event before the banner is shown, allowing developers to
measure user interaction
with the feature. Developers are also now able to
offer the banner for their native Android app
.
ES6 computed property names
Until now, developers defining a JavaScript
object literal
needed to know the names of all of its properties before runtime. This release increase the expressiveness of the object literal syntax by providing support for
ES6 computed property names
, allowing developers to put an expression in brackets [], to be computed as the property name at runtime.
let propertyName = "foo";
let obj = {
[propertyName + "IsTrue"]: true,
contains: 12
};
Other updates in this release
Chrome’s implementation of the
Push API
has undergone
several minor breaking changes
in order to keep up to date with the evolving specification.
ES6
extended Unicode escape sequences
allow developers to use the extended set of Unicode characters in JavaScript string literals, where previously characters whose escape sequences contain more than four hexadecimal values were unable to be denoted.
This release includes a new implementation of
multi-column layout
by Opera engineer Morten Stenshorne, solving historic issues with incorrect column balancing.
Developers should now use the scroll attributes of
document.scrollingElement
instead of
document.body
as the latter has several
well known issues
.
As always, visit
chromestatus.com/features
for a complete overview of Chrome’s developer features, and circle
+Google Chrome Developers
for more frequent updates.
Posted by Peter Beverloo, Software Engineer and Notification Newsmaker
Labels
accessibility
1
benchmarks
1
beta
8
blink
1
chrome apps
3
Chrome Frame
1
chrome web store
26
chromeframe
3
chromeos
3
chromium
3
cloud print
1
dart
8
devtools
11
extensions
23
gdd
1
googlechrome
12
html5
11
incognito
1
javascript
3
linux
2
mac
1
mobile
2
na
1
native client
8
New Features
5
octane
1
open web
2
releases
2
rlz
1
security
30
spdy
2
ssl
2
v8
5
web intents
1
webaudio
3
webgl
7
webkit
5
webp
5
webrtc
4
websockets
5
webtiming
1
Archive
2018
Jul
Jun
May
Apr
Mar
Feb
Jan
2017
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2016
Dec
Nov
Oct
Sep
Aug
Jun
May
Apr
Mar
Feb
Jan
2015
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2014
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2013
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2012
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2011
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2010
Dec
Nov
Oct
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2009
Dec
Nov
Sep
Aug
Jul
Jun
May
Apr
Mar
Feb
Jan
2008
Dec
Nov
Oct
Sep
Feed
Google
on
Follow @ChromiumDev
Give us feedback in our
Product Forums
.
