person:paul irish

The protocol-relative URL - Paul Irish
►https://www.paulirish.com/2010/the-protocol-relative-url

L’astuce pour requeter des ressources hors domaine depuis un site en httpS
<img src=’//domain.com/img/logo.png’>
et
.omgomg { background : url(//domain.net/image.gif) ;}

#https #astuce #ressource_externe

#bogue_seenthis : mettre le code src=//domain.com/img/logo.png avec l’URL entre guillemets doubles provoque son remplacement en https: //seenthis.net///domain.com/img/logo.png

The protocol-relative URL - Paul Irish
►https://www.paulirish.com/2010/the-protocol-relative-url

“If the asset you need is available on SSL, then always use the https:// asset.”

#URL_protocol_resource_relative_HTTPS

Ughck. #Images. - daverupert.com
▻http://daverupert.com/2013/06/ughck-images

The problem is so damn complex, it’s no wonder people are throwing in the towel on images, but for me it keeps coming down to one core thing. According to Paul Irish’s talk at Breaking Development, the Mobile Web is in trouble:

“There’s a common perception that mobile Web experiences are inferior to native mobile experiences. Many companies are building native experiences instead of #Web experiences.” – Paul Irish transcribed by LukeW

If the web cannot keep pace with a native experience in speed (rendering in under 1000ms), we’re all going to be out of the job

Paul Irish publie une liste de développeurs qu’il admire (dans le domaine du Web). Ça donne évidemment une excellente liste de liens :
►http://paulirish.com/2012/developers-we-admire

One of the good things about having the eyeballs of many people is that you now have the ability to throw other people into the limelight that completely deserve to be in it. Divya Manian and I have been, for a while now, putting together a list of people in the front-end development community who, in our opinion, could use more broad acknowledgment and attention.

Browser Market Pollution: IE[x] is the new IE6 « Paul Irish
►http://paulirish.com/2011/browser-market-pollution-iex-is-the-new-ie6

if [Microsoft] maintain the same policy, IE17 be released in 2019, before IE8, 9 and 10 finally die. So in a few years from now, you’ll be supporting one version of Chrome, one version of Firefox, one of Opera, (probably) one of Safari, and ten versions of IE.

http://static.arstechnica.com/browsers-july-2011/internet-explorer-transition.png http://static.arstechnica.com/browsers-july-2011/chrome-transition.png

The protocol-relative URL « Paul Irish
►http://paulirish.com/2010/the-protocol-relative-url

Une petite astuce que je ne connaissais pas :

There’s this little trick you can get away with that’ll save you some headaches:

<a href="//domain.com/toto.html">

If the browser is viewing that current page in through HTTPS, then it’ll request that asset with the HTTPS protocol, otherwise it’ll typically* request it with HTTP. This prevents that awful “This Page Contains Both Secure and Non-Secure Items” error message in IE, keeping all your asset requests within the same protocol.

Note : dans l’article original la balise HTML d’exemple est un <img>, mais #seenthis rajoute automatiquement le "http:" manquant devant.

Apparemment ça marche aussi avec file ://

Initializr - Start your HTML5 project in 15 seconds !
►http://www.initializr.com

Initializr is an #HTML5 templates generator to help you getting started with an HTML5 project. It is built on HTML5 Boilerplate, a powerful HTML5 template created by Paul Irish and Divya Manian. Initializr will generate for you a clean customizable template based on Boilerplate with just what you need to start.

Basé sur HTML5 Boilerplate :

►http://html5boilerplate.com

The Story of the HTML5 Shiv « Paul Irish
►http://paulirish.com/2011/the-history-of-the-html5-shiv

Fast forward to 2008, HTML5 is gaining momentum. New elements have been specified, however in practice, Internet Explorer 6-8 pose a problem as they do not recognize unknown elements; the new elements cannot hold children and are unaffected by CSS. This sad fact was posing quite a big hinderance to HTML5 adoption.

Sympathique billet de Paul Irish, qui raconte comment un certain Sjoerd Visscher a découvert comment « activer » les nouvelles balises du #HTML5 dans #Internet_Explorer, permettant ainsi l’utilisation dès à présent du HTML5.

The New Bulletproof Font-Face Syntax | Fontspring
►http://www.fontspring.com/blog/the-new-bulletproof-font-face-syntax

In September 2009, Paul Irish came up with the Bulletproof syntax for writing the font-face declaration. It was compact and worked across all browsers at the time. Recent, growing complaints that fonts weren’t loading in Android, led us to recommended the Mo’ Bulletproofer syntax devised by Richard Fink instead. Unfortunately Mo’ Bulletproofer requires double declarations and is therefore harder to maintain.

Merci @fil The New Bulletproof #Font-Face Syntax | Fontspring
►http://www.fontspring.com/blog/the-new-bulletproof-font-face-syntax

In September 2009, Paul Irish came up with the Bulletproof syntax for writing the font-face declaration. It was compact and worked across all browsers at the time. Recent, growing complaints that fonts weren’t loading in Android, led us to recommended the Mo’ Bulletproofer syntax devised by Richard Fink instead. Unfortunately Mo’ Bulletproofer requires double declarations and is therefore harder to maintain.

#typographie