J'ai besoin d'intimité. Non pas parce que mes actions sont douteuses, mais parce que votre jugement et vos intentions le sont.
5178 links
Instead of installing $your-framework-autosuggest, try out datalist in your next project. Datalist is the browsers built-in way of showing a list of options as a user types into an input.
<input list="frameworks" />
<datalist id="frameworks">
<option>Bootstrap</option>
<option>Tailwind CSS</option>
<option>Foundation</option>
<option>Bulma</option>
<option>Skeleton</option>
</datalist>
To use it, you add a datalist element with an ID and a set of options to your HTML. Don't worry, the element won't be visible. Then you use the list attribute on an input to associate the two.
As a user now types into the input, the browser will show the datalist as a dropdown, automatically filtering the options as the user types. Because it's a regular input though, users still have the option to type in their own value. Lastly, they can see all of the options by selecting the input and using the arrow keys to navigate the list, or clicking the dropdown icon the browser adds.
Encore un excellent tuto de SebSauvage.
Que serait le web français sans lui ???
Merci Seb !!!
<table class=”events-table” >
<caption>Évènements</caption>
<thead>
<tr>
<th class=”event-date”>Date</th>
<th class=”event-time”>Horaire</th>
<th class=”event-description”>Evènement</th>
</tr>
</thead>
<tbody>
<tr>
<td data-label=”Date”> Le #_EVENTDATES</td>
<td data-label=”Horaire”>#_EVENTTIMES</td>
<td data-label=”Evènement”>#_EVENTLINK</td>
</tr>
</tbody>
</table>
Je pense à ajouter un “data-label” à chacun de mes “td”.
Et voici le CSS :
table caption {
display: none;
}
@media all and (max-width:500px){
table{
width:100%;
}
table caption {
display: block;
background-color: #484d55;
color:white;
}
.table thead {
display: none;
}
.table tr{
display: block;
margin-bottom: 40px;
}
.table td {
display: block;
text-align: right;
}
.table td:before {
content: attr(data-label);
float: left;
font-weight: bold;
}
}Ne fonctionne que sous Chrome...
=> poubelle (même si ça semble pas mal)
Ajouter un mot de passe à n'importe quelle url.
Encoder une page dans l'url en base64, à la manière de zerobin.
Des onglets en css pur.
D'autres solutions ici : https://github.com/you-dont-need/You-Dont-Need-JavaScript
Via SebSauvage
Il m'en manque 4...
a
html
body
head
footer
div
span
p
article
dd
dt
th
thead
tbody
td
caption
h1
h2
h3
h4
h5
h6
ul
li
ol
meta
link
style
script
b
u
small
i
aside
video
object
iframe
audio
svg
details
summary
dialog
data
base
meter
progress
nav
label
form
input
textarea
fieldset
button
pre
code
section
time
img
blockquote
strong
title
br
template
main
em
dl
datalist
option
del
optgroup
select
embed
output
canvas
source
track
col
tfoot
table
tr
q
cite
abbr
address
sup
sub
var
kbd
samp
hr
noscript
s
map
figure
figcaption
ins
dfn
bdi
bdo
mark
rb
rp
rt
ruby
wbr
area
param
hgroup
picture
slot
math
Le schéma pour les recettes de cuisine
Pour remplacer les puces par des images (ou changer le style de la puce), il faut placer la règle css dans la balise ul, sinon, dans la balise <style type="text/css">, ça ne fonctionne pas.
Un cv en JSON. Plusieurs thèmes possible.
Extremely short version
Instead of serving dozens of icons, all you need is just five icons and one JSON file.
In your HTML, for the browser:
<link rel="icon" href="/favicon.ico" /><!-- 32×32 --> <link rel="icon" href="/icon.svg" type="image/svg+xml" sizes="any" /> <link rel="apple-touch-icon" href="/apple.png" /><!-- 180×180 --> <link rel="manifest" href="/manifest.webmanifest" />And in your web app manifest:
// manifest.webmanifest { "icons": [ { "src": "/192.png", "type": "image/png", "sizes": "192x192" }, { "src": "/512.png", "type": "image/png", "sizes": "512x512" } ] }
C'est dans la même veine que le DOM Sahdow de Facebook ?
Pour réaliser des présentations simples mais propres en markdown.
Un peu d'histoire du web. Dire qu'on a connu ça, ça ne nous rajeunit pas...
Intéressant car souvent Zeal plante avec les docs MDN
Checkboxes and radio buttons are two common examples of interactive form elements that we desperately want to have full control over styling but we don’t. So we’ve been hacking our way around styling them by hiding said elements with CSS and visually replacing them with pseudo-elements or an SVG image — SVG, of course, being the more flexible, powerful, and accessible replacement. But an SVG image is, at the end of the day, just an image, so while it can visually replace a checkbox, it doesn’t really substitute for it — the user still needs a checkbox to interact with. So, when we attempt to hide the checkbox we want to style, we need to make sure that the checkbox remains accessible and interactive.
Autant le design est pas mal, autant faire appel à docker, jquery et consort pour une simple page html, c'est un peu abusé je trouve.