Paul Irish on Chrome Moving to Blink
I know you’ve been asked this plenty of times already, but: no new vendor prefixes, right? Right? Nope, none! They’re great in theory but turns out they fail in practice, so we’re joining Mozilla and the W3C CSS WG and moving away them. There’s a few parts to this. Firstly, we won’t be migrating the existing -webkit- prefixed properties to a -chrome- or -blink- prefix, that’d just make extra work for everyone. Secondly, we inherited some existing properties that are prefixed. Some, like -webkit-transform , are standards track and we work with the CSS WG to move ahead those standards while we fix any remaining issues in our implementation and we’ll unprefix them when they’re ready. Others, like -webkit-box-reflect are not standards track and we’ll bring them to standards bodies or responsibly deprecate these on a case-by-case basis. Lastly, we’re not introducing any new CSS properties behind a prefix. Pinky swear? Totes. New stuff will be available to experiment with behind ...
adobe
ambitions
android
apple
applications
blink-powered
canary
chris
chrome
chromebook
chromeos
chromium
coffeescript
commitment
compatibility
confirmation
conformance
css
darin
dart
decision
deprecation
dev
development
devtools
divergence
dom
emscripten
expectations
experience
experiment
firstly
fisher
freedom
google
haha
implementation
integration
interoperability
ios
irish
javascript
javascriptcore
lastly
limitations
linux
mac
maintenance
management
mention
mozilla
non-webkit
nope
oilpan
opera
paul
performance
pinky
policy
practice
priority
quality
rangeexception
recalculation
resistance
safari
scalability
secondly
simplicity
technology
tradition
typescript
vbscript-y
version
webkit
webkit-based
wilson
windows
xmlhttprequestexception
After Testing It With Facebook Messenger, Mozilla Signs Up Weibo, Mixi, MSN Now And CliqZ To Firefox's Social API
Last November, Mozilla announced that it had worked with Facebook to launch a first preview of its Social API for Firefox by integrating Facebook Messenger into Firefox 17. The Social API allows social networks, blog networks or news sites to easily add persistent social sidebars, toolbar notifications and chat features to the browser, no matter which site a user is looking at. At the time, Mozilla wasn’t quite ready to announce any additional partners for this API. But today the organization announced that it will soon expand this effort with additional services in Firefox Nightly, including Japanese social network Mixi, Microsoft’s MSN Now, new site, CliqZ and the Chinese microblogging service Weibo. “We are really excited about the possibilities that Social API brings to the future of browsing, including ways to integrate even more social providers, e-mail, finance, news and other applications and services into your Firefox experience,” Mozilla writes in today’s announcement. ...
announcement
api
applications
chinese
cliqz
experience
facebook
finance
firefox
integration
japanese
jonathan
limitations
messenger
microsoft
mixi
mozilla
msn
nightingale
notifications
organization
possibility
service
solution
weibo
The Era of Symbol Fonts
Improving performance is a constant process. First we ditched tables, spacer gifs, and inline markup such as the <font> element in favor of CSS, reducing page sizes, and separating style from layout. Then we became aware of all our DNS requests, caching, and the total number of files and started using CSS sprites, moving many small images out of the HTML and into a single background image. Now it’s time we embrace the third epoch in performance optimization: symbol fonts. Embedding a symbol font lets us move some of those tiny icons into a single font file rather than a sprite. This has the same caching and file size benefits as a CSS sprite, as well as some additional benefits we’re only now realizing with high-resolution displays. In this article, I’ll walk you through some of the advantages and issues you’ll encounter when using a symbol font. A smooth experience As the number of fonts designed for use as icons, glyphs, and decorations increase, several high-traffic websites ...
ability
accessibility
apple
applications
ascii
audience
bbc
canvas
convergence
conversion
creation
css
decorations
density
devices
dns
elements
emoji
existence
experience
flash
fontforge
github
html
icomoon
instance
interoperability
javascript
limitations
lion
navigation
non-flash
non-javascript
octicons
opportunity
optimization
options
osx
pdf
performance
photoshop
possibility
practice
random
raphaeljs
reality
resolution
sequence
service
simplicity
situation
solution
substitution
svg
technology
thickness
unicode
utility
vml
Does Spotify Need A Web Player? (Of Course It Does)
News broke out today that Spotify would be making a beta version of its web player available to all of its users in the UK, with the promise that a full release would come later this year. I’m not complaining that I’ll soon be able to access Spotify through my browser. But why is Spotify, well established streaming music juggernaut that it is, using its resources to make this happen? In other words, does Spotify need a web player? It isn’t as if there are a growing number of Chromebook users out there that are just itching to get their streaming music action on. A new report released Monday revealed that Chromebooks accounted for only 0.07% of desktop and laptop web traffic. The fruit there isn’t ripe for picking. In fact, the fruit there hasn’t even started growing at all. Spotify’s main competitor in this space, Rdio, runs completely off desktop, mobile, and web applications. But the notion that Rdio is scaring Spotify into making a play in this web player space is laughable. ...
accessibility
action
appdata
applications
chromebook
chromebooks
constine
function
internet connection
josh
limitations
linux
million
notion
playlists
rdio
spotify
version
Your Website has Two Faces
Like the Roman god Janus (and many a politician), every web application has two faces: Its human face interacts with people, while its machine face interacts with computer systems, often as a result of those human interactions. Showing too much of either face to the wrong audience creates opportunity for error. When a user interface—intended for human consumption—reflects too much of a system’s internals in its design and language, it’s likely to confuse the people who use it. But at the same time, if data doesn’t conform to a specific structure, it’s likely to confuse the machines that need to use it—so we can’t ignore system requirements, either. People and machines parse information in fundamentally different ways. We need to find a way to balance the needs of both. Enter the Robustness Principle In 1980, computer scientist Jon Postel published an early specification for the Transmission Control Protocol, which remains the fundamental communication mechanism of the internet. ...
abbreviation
action
alice
api
appia
applications
assumption
audience
avenue
balance
bob
business
circumstances
communications
confirmation
consumption
convenience
crm
currency
definition
description
donations
elements
exception
expectations
experience
expression
geneva
genève
geocoding
google
granularity
html
influence
information
instructions
integrity
interaction
interpretation
janus
javascript
jon
limitations
locality
majority
mechanism
normalcy
notifications
occurrence
opportunity
postel
preferences
priority
reduction
requirements
responsibility
robustness
roman
sanity
scientists
service
specification
standardization
suisse
switzerland
tcp
thu
transactions
transmission
unfortunately
unix-based
validation
yyyy