Browse Source

Publishing

master
David Larlet 1 month ago
parent
commit
13448c4f7d

+ 2
- 2
david/2021/03/21/index.html View File

@@ -62,7 +62,7 @@
<a href="/david/" title="Aller à l’accueil"><svg class="icon icon-home">
<use xlink:href="/static/david/icons2/symbol-defs.svg#icon-home"></use>
</svg> Accueil</a>
• <a rel="next" href="/david/2021/03/22/" title="Publication suivante : JavaScript-less">Suivant →</a>
</p>
</nav>
<hr>
@@ -81,7 +81,7 @@
<p class="center">
<a rel="prev" href="/david/2021/03/20/" title="Publication précédente : Manuel">← Précédent</a> •
<a href="/david/2021/" title="Liste des publications récentes">↑ En 2021</a>
• <a rel="next" href="/david/2021/03/22/" title="Publication suivante : JavaScript-less">Suivant →</a>
</p>
</nav>
</article>

+ 183
- 0
david/2021/03/22/index.html View File

@@ -0,0 +1,183 @@
<!doctype html><!-- This is a valid HTML5 document. -->
<!-- Screen readers, SEO, extensions and so on. -->
<html lang="fr">
<!-- Has to be within the first 1024 bytes, hence before the <title>
See: https://www.w3.org/TR/2012/CR-html5-20121217/document-metadata.html#charset -->
<meta charset="utf-8">
<!-- Why no `X-UA-Compatible` meta: https://stackoverflow.com/a/6771584 -->
<!-- The viewport meta is quite crowded and we are responsible for that.
See: https://codepen.io/tigt/post/meta-viewport-for-2015 -->
<meta name="viewport" content="width=device-width,initial-scale=1">
<!-- Required to make a valid HTML5 document. -->
<title>JavaScript-less — David Larlet</title>
<meta name="description" content="With a few minor omissions and links, you can create a site that works great in modern browsers with ES6+ and acceptably in browsers without JavaScript. This approach is more sustainable for teams without the resources for extensive QA, and more beneficial to users of nonstandard browsers. […] The best way to help your IE11 users is to provide a great experience for your non-JS users and share that experience with them, instead of sending them an untested and buggy experience that also slows the experience of users with modern browsers.">
<!-- That good ol' feed, subscribe :). -->
<link rel="alternate" type="application/atom+xml" title="Feed" href="/david/log/">
<!-- Generated from https://realfavicongenerator.net/ such a mess. -->
<link rel="apple-touch-icon" sizes="180x180" href="/static/david/icons2/apple-touch-icon.png">
<link rel="icon" type="image/png" sizes="32x32" href="/static/david/icons2/favicon-32x32.png">
<link rel="icon" type="image/png" sizes="16x16" href="/static/david/icons2/favicon-16x16.png">
<link rel="manifest" href="/static/david/icons2/site.webmanifest">
<link rel="mask-icon" href="/static/david/icons2/safari-pinned-tab.svg" color="#07486c">
<link rel="shortcut icon" href="/static/david/icons2/favicon.ico">
<meta name="msapplication-TileColor" content="#f0f0ea">
<meta name="msapplication-config" content="/static/david/icons2/browserconfig.xml">
<meta name="theme-color" content="#f0f0ea">
<!-- Documented, feel free to shoot an email. -->
<link rel="stylesheet" href="/static/david/css/style_2021-01-20.css">
<!-- See https://www.zachleat.com/web/comprehensive-webfonts/ for the trade-off. -->
<link rel="preload" href="/static/david/css/fonts/triplicate_t4_poly_regular.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: light), (prefers-color-scheme: no-preference)" crossorigin>
<link rel="preload" href="/static/david/css/fonts/triplicate_t4_poly_bold.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: light), (prefers-color-scheme: no-preference)" crossorigin>
<link rel="preload" href="/static/david/css/fonts/triplicate_t4_poly_italic.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: light), (prefers-color-scheme: no-preference)" crossorigin>
<link rel="preload" href="/static/david/css/fonts/triplicate_t3_regular.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: dark)" crossorigin>
<link rel="preload" href="/static/david/css/fonts/triplicate_t3_bold.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: dark)" crossorigin>
<link rel="preload" href="/static/david/css/fonts/triplicate_t3_italic.woff2" as="font" type="font/woff2" media="(prefers-color-scheme: dark)" crossorigin>
<script>
function toggleTheme(themeName) {
document.documentElement.classList.toggle(
'forced-dark',
themeName === 'dark'
)
document.documentElement.classList.toggle(
'forced-light',
themeName === 'light'
)
}
const selectedTheme = localStorage.getItem('theme')
if (selectedTheme !== 'undefined') {
toggleTheme(selectedTheme)
}
</script>

<body class="remarkdown h1-underline h2-underline h3-underline em-underscore hr-center ul-star pre-tick" data-instant-intensity="viewport-all">


<article>
<header>
<h1>JavaScript-less</h1>
</header>
<nav>
<p class="center">
<a rel="prev" href="/david/2021/03/21/" title="Publication précédente : Gimbal">← Précédent</a> •
<a href="/david/" title="Aller à l’accueil"><svg class="icon icon-home">
<use xlink:href="/static/david/icons2/symbol-defs.svg#icon-home"></use>
</svg> Accueil</a>
</p>
</nav>
<hr>


<blockquote lang="en">
<p>With a few minor omissions and links, you can create a site that <strong>works great in modern browsers with ES6+</strong> <em>and</em> <strong>acceptably in browsers without JavaScript</strong>. This approach is more sustainable for teams without the resources for extensive QA, and more beneficial to users of nonstandard browsers. […]<br />
The best way to help your IE11&nbsp;users is <mark>to provide a great experience for your non-JS users</mark> and share that experience with them, instead of sending them an untested and buggy experience that also slows the experience of users with modern browsers.</p>
<p><cite><em><a href="https://blog.carlmjohnson.net/post/2020/time-to-kill-ie11/">Dropping Support For IE11&nbsp;Is Progressive Enhancement</a></em> (<a href="/david/cache/2021/a9e4daf32281eaee0adaa39e32d28890/">cache</a>)</cite></p>
</blockquote>
<p>Je trouve cette approche particulièrement pertinente, un peu difficile avec une <abbr title="Single Page App">SPA</abbr> sans serveur tout de même. Et encore, il y aurait des choses à expérimenter&nbsp;: on peut potentiellement aller très loin en CSS uniquement avec des <code>:checked</code> par exemple. À voir à quel point est-ce que ça endommage l’accessibilité par ailleurs… les défis techniques hypothétiques sont parfois de fausses bonnes idées pour des usages qui sont eux bien réels.</p>
<p>Les tests utilisateur·ices sont une source intarissable de découvertes impensables. <em>Qu’il faut pourtant panser.</em></p>

<nav>
<p class="center">
<a rel="prev" href="/david/2021/03/21/" title="Publication précédente : Gimbal">← Précédent</a> •
<a href="/david/2021/" title="Liste des publications récentes">↑ En 2021</a>
</p>
</nav>
</article>


<hr>

<footer>
<p>
<a href="/david/" title="Aller à l’accueil"><svg class="icon icon-home">
<use xlink:href="/static/david/icons2/symbol-defs.svg#icon-home"></use>
</svg> Accueil</a> •
<a href="/david/log/" title="Accès au flux RSS"><svg class="icon icon-rss2">
<use xlink:href="/static/david/icons2/symbol-defs.svg#icon-rss2"></use>
</svg> RSS</a> •
<a href="http://larlet.com" title="Go to my English profile" data-instant><svg class="icon icon-user-tie">
<use xlink:href="/static/david/icons2/symbol-defs.svg#icon-user-tie"></use>
</svg> Pro</a> •
<a href="mailto:david%40larlet.fr" title="Envoyer un courriel"><svg class="icon icon-mail">
<use xlink:href="/static/david/icons2/symbol-defs.svg#icon-mail"></use>
</svg> Email</a> •
<abbr class="nowrap" title="Hébergeur : Alwaysdata, 62 rue Tiquetonne 75002 Paris, +33184162340"><svg class="icon icon-hammer2">
<use xlink:href="/static/david/icons2/symbol-defs.svg#icon-hammer2"></use>
</svg> Légal</abbr>
</p>
<template id="theme-selector">
<form>
<fieldset>
<legend><svg class="icon icon-brightness-contrast">
<use xlink:href="/static/david/icons2/symbol-defs.svg#icon-brightness-contrast"></use>
</svg> Thème</legend>
<label>
<input type="radio" value="auto" name="chosen-color-scheme" checked> Auto
</label>
<label>
<input type="radio" value="dark" name="chosen-color-scheme"> Foncé
</label>
<label>
<input type="radio" value="light" name="chosen-color-scheme"> Clair
</label>
</fieldset>
</form>
</template>
</footer>
<script src="/static/david/js/instantpage-5.1.0.min.js" type="module"></script>
<script>
function loadThemeForm(templateName) {
const themeSelectorTemplate = document.querySelector(templateName)
const form = themeSelectorTemplate.content.firstElementChild
themeSelectorTemplate.replaceWith(form)

form.addEventListener('change', (e) => {
const chosenColorScheme = e.target.value
localStorage.setItem('theme', chosenColorScheme)
toggleTheme(chosenColorScheme)
})

const selectedTheme = localStorage.getItem('theme')
if (selectedTheme && selectedTheme !== 'undefined') {
form.querySelector(`[value="${selectedTheme}"]`).checked = true
}
}

const prefersColorSchemeDark = '(prefers-color-scheme: dark)'
window.addEventListener('load', () => {
let hasDarkRules = false
for (const styleSheet of Array.from(document.styleSheets)) {
let mediaRules = []
for (const cssRule of styleSheet.cssRules) {
if (cssRule.type !== CSSRule.MEDIA_RULE) {
continue
}
// WARNING: Safari does not have/supports `conditionText`.
if (cssRule.conditionText) {
if (cssRule.conditionText !== prefersColorSchemeDark) {
continue
}
} else {
if (cssRule.cssText.startsWith(prefersColorSchemeDark)) {
continue
}
}
mediaRules = mediaRules.concat(Array.from(cssRule.cssRules))
}

// WARNING: do not try to insert a Rule to a styleSheet you are
// currently iterating on, otherwise the browser will be stuck
// in a infinite loop…
for (const mediaRule of mediaRules) {
styleSheet.insertRule(mediaRule.cssText)
hasDarkRules = true
}
}
if (hasDarkRules) {
loadThemeForm('#theme-selector')
}
})
</script>
</body>
</html>

+ 2
- 0
david/2021/index.html View File

@@ -216,6 +216,8 @@
<h2><a href="/david/2021/03/21/">Gimbal</a> (2021-03-21)</h2>
<h2><a href="/david/2021/03/22/">JavaScript-less</a> (2021-03-22)</h2>
</main>



+ 10
- 0
david/2021/sources/2021-03-22 - JavaScript-less.md View File

@@ -0,0 +1,10 @@
# JavaScript-less

> [en] With a few minor omissions and links, you can create a site that **works great in modern browsers with ES6+** *and* **acceptably in browsers without JavaScript**. This approach is more sustainable for teams without the resources for extensive QA, and more beneficial to users of nonstandard browsers. […]
> The best way to help your IE11 users is ==to provide a great experience for your non-JS users== and share that experience with them, instead of sending them an untested and buggy experience that also slows the experience of users with modern browsers.
>
> <cite>*[Dropping Support For IE11 Is Progressive Enhancement](https://blog.carlmjohnson.net/post/2020/time-to-kill-ie11/)* ([cache](/david/cache/2021/a9e4daf32281eaee0adaa39e32d28890/))</cite>

Je trouve cette approche particulièrement pertinente, un peu difficile avec une <abbr title="Single Page App">SPA</abbr> sans serveur tout de même. Et encore, il y aurait des choses à expérimenter : on peut potentiellement aller très loin en CSS uniquement avec des `:checked` par exemple. À voir à quel point est-ce que ça endommage l’accessibilité par ailleurs… les défis techniques hypothétiques sont parfois de fausses bonnes idées pour des usages qui sont eux bien réels.

Les tests utilisateur·ices sont une source intarissable de découvertes impensables. *Qu’il faut pourtant panser.*

+ 2
- 0
david/index.html View File

@@ -74,6 +74,8 @@
<nav>
<ul>
<li><a href="/david/2021/03/22/">JavaScript-less</a> (2021-03-22)</li>
<li><a href="/david/2021/03/21/">Gimbal</a> (2021-03-21)</li>
<li><a href="/david/2021/03/20/">Manuel</a> (2021-03-20)</li>

+ 18
- 1
david/log/index.xml View File

@@ -5,13 +5,30 @@
<link href="https://larlet.fr/david/" rel="alternate" type="text/html" />
<link href="https://larlet.fr/david/log/" rel="self" />
<id>https://larlet.fr/david/</id>
<updated>2021-03-28T12:00:00+01:00</updated>
<updated>2021-03-29T12:00:00+01:00</updated>
<author>
<name>David Larlet</name>
<uri>https://larlet.fr/david/</uri>
</author>
<rights>Copyright (c) 2004-2021, David Larlet</rights>
<entry xml:lang="fr">
<title>JavaScript-less</title>
<link href="https://larlet.fr/david/2021/03/22/" rel="alternate" type="text/html" />
<updated>2021-03-22T12:00:00+01:00</updated>
<id>https://larlet.fr/david/2021/03/22/</id>
<summary type="html">

&lt;blockquote lang=&quot;en&quot;&gt;
&lt;p&gt;With a few minor omissions and links, you can create a site that &lt;strong&gt;works great in modern browsers with ES6+&lt;/strong&gt; &lt;em&gt;and&lt;/em&gt; &lt;strong&gt;acceptably in browsers without JavaScript&lt;/strong&gt;. This approach is more sustainable for teams without the resources for extensive QA, and more beneficial to users of nonstandard browsers. […]&lt;br /&gt;
The best way to help your IE11&amp;nbsp;users is &lt;mark&gt;to provide a great experience for your non-JS users&lt;/mark&gt; and share that experience with them, instead of sending them an untested and buggy experience that also slows the experience of users with modern browsers.&lt;/p&gt;
&lt;p&gt;&lt;cite&gt;&lt;em&gt;&lt;a href=&quot;https://blog.carlmjohnson.net/post/2020/time-to-kill-ie11/&quot;&gt;Dropping Support For IE11&amp;nbsp;Is Progressive Enhancement&lt;/a&gt;&lt;/em&gt; (&lt;a href=&quot;https://larlet.fr/david/cache/2021/a9e4daf32281eaee0adaa39e32d28890/&quot;&gt;cache&lt;/a&gt;)&lt;/cite&gt;&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;Je trouve cette approche particulièrement pertinente, un peu difficile avec une &lt;abbr title=&quot;Single Page App&quot;&gt;SPA&lt;/abbr&gt; sans serveur tout de même. Et encore, il y aurait des choses à expérimenter&amp;nbsp;: on peut potentiellement aller très loin en CSS uniquement avec des &lt;code&gt;:checked&lt;/code&gt; par exemple. À voir à quel point est-ce que ça endommage l’accessibilité par ailleurs… les défis techniques hypothétiques sont parfois de fausses bonnes idées pour des usages qui sont eux bien réels.&lt;/p&gt;
&lt;p&gt;Les tests utilisateur·ices sont une source intarissable de découvertes impensables. &lt;em&gt;Qu’il faut pourtant panser.&lt;/em&gt;&lt;/p&gt;
&lt;hr/&gt;&lt;p&gt;&lt;a href=&quot;mailto:david@larlet.fr&quot;&gt;Réagir ?&lt;/a&gt;&lt;/p&gt;</summary>
</entry>
<entry xml:lang="fr">
<title>Gimbal</title>
<link href="https://larlet.fr/david/2021/03/21/" rel="alternate" type="text/html" />

Loading…
Cancel
Save