Fossil SCM
Comment improvement on the "nomargins" section, and fixed up a few places where it wasn't as orthogonal as it should be.
Commit
f550c17d34476c30dc7df228ac867dda498d8c9d5accd377d9f24909ae77d672
Parent
d55d9b2a42f10d3…
1 file changed
+13
-2
+13
-2
| --- skins/default/css.txt | ||
| +++ skins/default/css.txt | ||
| @@ -279,12 +279,21 @@ | ||
| 279 | 279 | |
| 280 | 280 | div.pikchr-wrapper.indent:not(.source) { |
| 281 | 281 | margin-left: 70pt; |
| 282 | 282 | } |
| 283 | 283 | |
| 284 | -/* Back above margins out in forum posts and ticket comments, and define | |
| 285 | - * a one-off class for use in documents where the same is desired. */ | |
| 284 | +/* Back above margin changes out in sections where it isn't helpful, | |
| 285 | + * mainly forum posts — indented already on the desktop due to the | |
| 286 | + * default threaded view — and ticket comments. Also define a class | |
| 287 | + * for use in documents where the same effect is wanted in a one-off | |
| 288 | + * fashion, as with the ToC sidebar on the Fossil home page. | |
| 289 | + * | |
| 290 | + * If you're wondering why this is so repetitive, it's to ensure that | |
| 291 | + * we back out all hierarchical levels of formatting inversely. In a | |
| 292 | + * richer stylesheet language like SCSS, we could express the hierarchy | |
| 293 | + * directly, getting the same effect in a small fraction of the code. | |
| 294 | + */ | |
| 286 | 295 | .forum .markdown blockquote, |
| 287 | 296 | .forum .markdown h1, |
| 288 | 297 | .forum .markdown h2, |
| 289 | 298 | .forum .markdown h3, |
| 290 | 299 | .forum .markdown h4, |
| @@ -294,10 +303,11 @@ | ||
| 294 | 303 | .forum .markdown ol, |
| 295 | 304 | .forum .markdown ul, |
| 296 | 305 | .forum .forumTime h1, |
| 297 | 306 | .forum .forumTime h2, |
| 298 | 307 | .forum .forumTime h3, |
| 308 | +.tkt .markdown blockquote, | |
| 299 | 309 | .tkt .markdown h1, |
| 300 | 310 | .tkt .markdown h2, |
| 301 | 311 | .tkt .markdown h3, |
| 302 | 312 | .tkt .markdown h4, |
| 303 | 313 | .tkt .markdown h5, |
| @@ -304,10 +314,11 @@ | ||
| 304 | 314 | .tkt .markdown p, |
| 305 | 315 | .tkt .markdown pre, |
| 306 | 316 | .tkt .markdown ol, |
| 307 | 317 | .tkt .markdown ul, |
| 308 | 318 | .nomargins, |
| 319 | +.nomargins blockquote, | |
| 309 | 320 | .nomargins h1, |
| 310 | 321 | .nomargins h2, |
| 311 | 322 | .nomargins h3, |
| 312 | 323 | .nomargins h4, |
| 313 | 324 | .nomargins h5, |
| 314 | 325 |
| --- skins/default/css.txt | |
| +++ skins/default/css.txt | |
| @@ -279,12 +279,21 @@ | |
| 279 | |
| 280 | div.pikchr-wrapper.indent:not(.source) { |
| 281 | margin-left: 70pt; |
| 282 | } |
| 283 | |
| 284 | /* Back above margins out in forum posts and ticket comments, and define |
| 285 | * a one-off class for use in documents where the same is desired. */ |
| 286 | .forum .markdown blockquote, |
| 287 | .forum .markdown h1, |
| 288 | .forum .markdown h2, |
| 289 | .forum .markdown h3, |
| 290 | .forum .markdown h4, |
| @@ -294,10 +303,11 @@ | |
| 294 | .forum .markdown ol, |
| 295 | .forum .markdown ul, |
| 296 | .forum .forumTime h1, |
| 297 | .forum .forumTime h2, |
| 298 | .forum .forumTime h3, |
| 299 | .tkt .markdown h1, |
| 300 | .tkt .markdown h2, |
| 301 | .tkt .markdown h3, |
| 302 | .tkt .markdown h4, |
| 303 | .tkt .markdown h5, |
| @@ -304,10 +314,11 @@ | |
| 304 | .tkt .markdown p, |
| 305 | .tkt .markdown pre, |
| 306 | .tkt .markdown ol, |
| 307 | .tkt .markdown ul, |
| 308 | .nomargins, |
| 309 | .nomargins h1, |
| 310 | .nomargins h2, |
| 311 | .nomargins h3, |
| 312 | .nomargins h4, |
| 313 | .nomargins h5, |
| 314 |
| --- skins/default/css.txt | |
| +++ skins/default/css.txt | |
| @@ -279,12 +279,21 @@ | |
| 279 | |
| 280 | div.pikchr-wrapper.indent:not(.source) { |
| 281 | margin-left: 70pt; |
| 282 | } |
| 283 | |
| 284 | /* Back above margin changes out in sections where it isn't helpful, |
| 285 | * mainly forum posts — indented already on the desktop due to the |
| 286 | * default threaded view — and ticket comments. Also define a class |
| 287 | * for use in documents where the same effect is wanted in a one-off |
| 288 | * fashion, as with the ToC sidebar on the Fossil home page. |
| 289 | * |
| 290 | * If you're wondering why this is so repetitive, it's to ensure that |
| 291 | * we back out all hierarchical levels of formatting inversely. In a |
| 292 | * richer stylesheet language like SCSS, we could express the hierarchy |
| 293 | * directly, getting the same effect in a small fraction of the code. |
| 294 | */ |
| 295 | .forum .markdown blockquote, |
| 296 | .forum .markdown h1, |
| 297 | .forum .markdown h2, |
| 298 | .forum .markdown h3, |
| 299 | .forum .markdown h4, |
| @@ -294,10 +303,11 @@ | |
| 303 | .forum .markdown ol, |
| 304 | .forum .markdown ul, |
| 305 | .forum .forumTime h1, |
| 306 | .forum .forumTime h2, |
| 307 | .forum .forumTime h3, |
| 308 | .tkt .markdown blockquote, |
| 309 | .tkt .markdown h1, |
| 310 | .tkt .markdown h2, |
| 311 | .tkt .markdown h3, |
| 312 | .tkt .markdown h4, |
| 313 | .tkt .markdown h5, |
| @@ -304,10 +314,11 @@ | |
| 314 | .tkt .markdown p, |
| 315 | .tkt .markdown pre, |
| 316 | .tkt .markdown ol, |
| 317 | .tkt .markdown ul, |
| 318 | .nomargins, |
| 319 | .nomargins blockquote, |
| 320 | .nomargins h1, |
| 321 | .nomargins h2, |
| 322 | .nomargins h3, |
| 323 | .nomargins h4, |
| 324 | .nomargins h5, |
| 325 |