Fossil SCM
The inline "code" snippet styling in [4772a9b2] now applies to MD forum posts.
Commit
32c4522d730b448bf788b5ec2ce7be6e82bfb60782cf29f89dc8170e51678f4d
Parent
06a70ff8677fd08…
1 file changed
+17
-5
+17
-5
| --- skins/default/css.txt | ||
| +++ skins/default/css.txt | ||
| @@ -222,11 +222,11 @@ | ||
| 222 | 222 | |
| 223 | 223 | /* Mark inline code fragments in the near-universal manner pioneered by |
| 224 | 224 | * Stack Overflow, then picked up by approximately everyone, including |
| 225 | 225 | * us, now. |
| 226 | 226 | * |
| 227 | - * This combinatoric selector explosion results from a need to apply | |
| 227 | + * This combinatorial selector explosion results from a need to apply | |
| 228 | 228 | * these stylings inside multiple page container types, multiplied by |
| 229 | 229 | * the surprisingly large number of tags HTML defines for semantically |
| 230 | 230 | * differentiated monospaced inline markup. If we do not target the |
| 231 | 231 | * elements we want to affect carefully, we'll end up overreaching, |
| 232 | 232 | * styling Fossil UI elements that use these tags for local purposes. |
| @@ -236,25 +236,32 @@ | ||
| 236 | 236 | * Our limited intent here is to style user content only, where it is |
| 237 | 237 | * unreasonable to expect its author to take the time to hand-craft |
| 238 | 238 | * per-document styling. Contrast Fossil UI, which often does exactly |
| 239 | 239 | * that in order to get particular results. |
| 240 | 240 | * |
| 241 | - * The equivalent Sass syntax is far more compact, thus clearer: | |
| 241 | + * Its rough equivalent in Sass syntax is far more compact, thus clearer: | |
| 242 | 242 | * |
| 243 | - * .artifact, .dir, .doc, .wiki // the page types we target | |
| 243 | + * .artifact, .dir, .doc, .forum, .wiki // the page types we target | |
| 244 | 244 | * > .content // hands off header & footer |
| 245 | 245 | * &, > .fossil-doc, > .markdown // wiki, HTML & MD emb docs |
| 246 | 246 | * > p // inline elements only |
| 247 | 247 | * > code, > kbd, > samp, > tt, > var // monospaced tag types |
| 248 | 248 | * background-color: #eee // pale gray box that… |
| 249 | 249 | * padding: 0 4px // …extends around the sides |
| 250 | 250 | * |
| 251 | - * We generated the CSS below by: | |
| 251 | + * The CSS below is based on feeding that through this: | |
| 252 | 252 | * |
| 253 | 253 | * $ sassc code.sass | sed -e 's/, /,\n/g' |
| 254 | 254 | * |
| 255 | - * …then hand-cleansed it to make it _somewhat_ more understandable. | |
| 255 | + * …then hand-cleansing it to make it _somewhat_ more understandable. | |
| 256 | + * That largely amounts to whitespace tweaks, but we've also done things | |
| 257 | + * like trim back the forum-specific styling to apply to the default MD | |
| 258 | + * markup only; direct HTML formatting isn't even an option there, and | |
| 259 | + * while wiki markup _is_ supported, MD was the default from day 1. | |
| 260 | + * Another quirk of the forum post handling is that the .markdown class | |
| 261 | + * gets applied per-post, not up at the top level as with the wiki, | |
| 262 | + * embedded docs, etc. | |
| 256 | 263 | */ |
| 257 | 264 | .artifact > .content > p > code, |
| 258 | 265 | .artifact > .content > p > kbd, |
| 259 | 266 | .artifact > .content > p > samp, |
| 260 | 267 | .artifact > .content > p > tt, |
| @@ -297,10 +304,15 @@ | ||
| 297 | 304 | .doc > .content > .markdown > p > code, |
| 298 | 305 | .doc > .content > .markdown > p > kbd, |
| 299 | 306 | .doc > .content > .markdown > p > samp, |
| 300 | 307 | .doc > .content > .markdown > p > tt, |
| 301 | 308 | .doc > .content > .markdown > p > var, |
| 309 | +.forum > .content .markdown > p > code, | |
| 310 | +.forum > .content .markdown > p > kbd, | |
| 311 | +.forum > .content .markdown > p > samp, | |
| 312 | +.forum > .content .markdown > p > tt, | |
| 313 | +.forum > .content .markdown > p > var, | |
| 302 | 314 | .wiki > .content > p > code, |
| 303 | 315 | .wiki > .content > p > kbd, |
| 304 | 316 | .wiki > .content > p > samp, |
| 305 | 317 | .wiki > .content > p > tt, |
| 306 | 318 | .wiki > .content > p > var, |
| 307 | 319 |
| --- skins/default/css.txt | |
| +++ skins/default/css.txt | |
| @@ -222,11 +222,11 @@ | |
| 222 | |
| 223 | /* Mark inline code fragments in the near-universal manner pioneered by |
| 224 | * Stack Overflow, then picked up by approximately everyone, including |
| 225 | * us, now. |
| 226 | * |
| 227 | * This combinatoric selector explosion results from a need to apply |
| 228 | * these stylings inside multiple page container types, multiplied by |
| 229 | * the surprisingly large number of tags HTML defines for semantically |
| 230 | * differentiated monospaced inline markup. If we do not target the |
| 231 | * elements we want to affect carefully, we'll end up overreaching, |
| 232 | * styling Fossil UI elements that use these tags for local purposes. |
| @@ -236,25 +236,32 @@ | |
| 236 | * Our limited intent here is to style user content only, where it is |
| 237 | * unreasonable to expect its author to take the time to hand-craft |
| 238 | * per-document styling. Contrast Fossil UI, which often does exactly |
| 239 | * that in order to get particular results. |
| 240 | * |
| 241 | * The equivalent Sass syntax is far more compact, thus clearer: |
| 242 | * |
| 243 | * .artifact, .dir, .doc, .wiki // the page types we target |
| 244 | * > .content // hands off header & footer |
| 245 | * &, > .fossil-doc, > .markdown // wiki, HTML & MD emb docs |
| 246 | * > p // inline elements only |
| 247 | * > code, > kbd, > samp, > tt, > var // monospaced tag types |
| 248 | * background-color: #eee // pale gray box that… |
| 249 | * padding: 0 4px // …extends around the sides |
| 250 | * |
| 251 | * We generated the CSS below by: |
| 252 | * |
| 253 | * $ sassc code.sass | sed -e 's/, /,\n/g' |
| 254 | * |
| 255 | * …then hand-cleansed it to make it _somewhat_ more understandable. |
| 256 | */ |
| 257 | .artifact > .content > p > code, |
| 258 | .artifact > .content > p > kbd, |
| 259 | .artifact > .content > p > samp, |
| 260 | .artifact > .content > p > tt, |
| @@ -297,10 +304,15 @@ | |
| 297 | .doc > .content > .markdown > p > code, |
| 298 | .doc > .content > .markdown > p > kbd, |
| 299 | .doc > .content > .markdown > p > samp, |
| 300 | .doc > .content > .markdown > p > tt, |
| 301 | .doc > .content > .markdown > p > var, |
| 302 | .wiki > .content > p > code, |
| 303 | .wiki > .content > p > kbd, |
| 304 | .wiki > .content > p > samp, |
| 305 | .wiki > .content > p > tt, |
| 306 | .wiki > .content > p > var, |
| 307 |
| --- skins/default/css.txt | |
| +++ skins/default/css.txt | |
| @@ -222,11 +222,11 @@ | |
| 222 | |
| 223 | /* Mark inline code fragments in the near-universal manner pioneered by |
| 224 | * Stack Overflow, then picked up by approximately everyone, including |
| 225 | * us, now. |
| 226 | * |
| 227 | * This combinatorial selector explosion results from a need to apply |
| 228 | * these stylings inside multiple page container types, multiplied by |
| 229 | * the surprisingly large number of tags HTML defines for semantically |
| 230 | * differentiated monospaced inline markup. If we do not target the |
| 231 | * elements we want to affect carefully, we'll end up overreaching, |
| 232 | * styling Fossil UI elements that use these tags for local purposes. |
| @@ -236,25 +236,32 @@ | |
| 236 | * Our limited intent here is to style user content only, where it is |
| 237 | * unreasonable to expect its author to take the time to hand-craft |
| 238 | * per-document styling. Contrast Fossil UI, which often does exactly |
| 239 | * that in order to get particular results. |
| 240 | * |
| 241 | * Its rough equivalent in Sass syntax is far more compact, thus clearer: |
| 242 | * |
| 243 | * .artifact, .dir, .doc, .forum, .wiki // the page types we target |
| 244 | * > .content // hands off header & footer |
| 245 | * &, > .fossil-doc, > .markdown // wiki, HTML & MD emb docs |
| 246 | * > p // inline elements only |
| 247 | * > code, > kbd, > samp, > tt, > var // monospaced tag types |
| 248 | * background-color: #eee // pale gray box that… |
| 249 | * padding: 0 4px // …extends around the sides |
| 250 | * |
| 251 | * The CSS below is based on feeding that through this: |
| 252 | * |
| 253 | * $ sassc code.sass | sed -e 's/, /,\n/g' |
| 254 | * |
| 255 | * …then hand-cleansing it to make it _somewhat_ more understandable. |
| 256 | * That largely amounts to whitespace tweaks, but we've also done things |
| 257 | * like trim back the forum-specific styling to apply to the default MD |
| 258 | * markup only; direct HTML formatting isn't even an option there, and |
| 259 | * while wiki markup _is_ supported, MD was the default from day 1. |
| 260 | * Another quirk of the forum post handling is that the .markdown class |
| 261 | * gets applied per-post, not up at the top level as with the wiki, |
| 262 | * embedded docs, etc. |
| 263 | */ |
| 264 | .artifact > .content > p > code, |
| 265 | .artifact > .content > p > kbd, |
| 266 | .artifact > .content > p > samp, |
| 267 | .artifact > .content > p > tt, |
| @@ -297,10 +304,15 @@ | |
| 304 | .doc > .content > .markdown > p > code, |
| 305 | .doc > .content > .markdown > p > kbd, |
| 306 | .doc > .content > .markdown > p > samp, |
| 307 | .doc > .content > .markdown > p > tt, |
| 308 | .doc > .content > .markdown > p > var, |
| 309 | .forum > .content .markdown > p > code, |
| 310 | .forum > .content .markdown > p > kbd, |
| 311 | .forum > .content .markdown > p > samp, |
| 312 | .forum > .content .markdown > p > tt, |
| 313 | .forum > .content .markdown > p > var, |
| 314 | .wiki > .content > p > code, |
| 315 | .wiki > .content > p > kbd, |
| 316 | .wiki > .content > p > samp, |
| 317 | .wiki > .content > p > tt, |
| 318 | .wiki > .content > p > var, |
| 319 |