-
Notifications
You must be signed in to change notification settings - Fork 23
Expand file tree
/
Copy pathSection-003.xhtml
More file actions
787 lines (550 loc) · 27.7 KB
/
Section-003.xhtml
File metadata and controls
787 lines (550 loc) · 27.7 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" xmlns:epub="http://www.idpf.org/2007/ops" xml:lang="en">
<head>
<meta charset="utf-8"/>
<meta name="generator" content="pandoc"/>
<title>Readium CSS Implementers’ doc</title>
<link rel="stylesheet" type="text/css" href="../Styles/stylesheet.css"/>
</head>
<body xml:lang="en">
<section id="inject-and-paginate-contents" class="level1">
<h1>Inject and paginate EPUB contents</h1>
<p>[Implementers’ doc] [Authors’ info]</p>
<section id="injection" class="level2">
<h2 id="sigil_toc_id_8">Injection</h2>
<p>Depending on the platform and version you’re developing for, contents must be injected into:</p>
<ul>
<li>a web view;</li>
<li>a chrome view;</li>
<li>an iframe.</li>
</ul>
<p>Indeed, we must provide authors with a reliable context in which their styles and scripts are scoped.</p>
<section id="margins-and-dimensions" class="level3">
<h3 class="sigil_not_in_toc">Margins and dimensions</h3>
<p>Since we must take viewport units into account, especially <code>vh</code> (viewport height), at least the top and bottom margins must be set on this container, and not inside it.</p>
<p>You may also want to set left and right margins on this container so that all margins are equal in the two-column view.</p>
<p>Finally, on larger screens, you’ll have to set dimensions on this container so that it doesn’t become too large.</p>
</section>
<section id="background-color" class="level3">
<h3 class="sigil_not_in_toc">Background color</h3>
<p>Please note you must deal with the <code>background-color</code> outside this container, especially as the user could set an arbitrary color through theming. In other words, it must be synced with this user setting so that the entire screen is the same <code>background-color</code>.</p>
<p>As a friendly reminder, you can allow transparency for the iframe if you’re using one. That should help deal with <code>background-color</code> at the global level.</p>
<pre><code><iframe src="source.xhtml" allowtransparency="true"></iframe></code></pre>
<p>Then set the <code>--RS__backgroundColor</code> variable to <code>transparent</code> in <code>ReadiumCSS-base.css</code>, although you will have to modify the current user settings stylesheet so that it can work this way.</p>
</section>
</section>
<section id="pagination" class="level2">
<h2 id="sigil_toc_id_9">Pagination</h2>
<p>Contents are paginated using <a href="https://www.w3.org/TR/css3-multicol/">CSS multicolumns</a>, for several reasons:</p>
<ul>
<li><a href="http://caniuse.com/#feat=multicolumn">it’s been cross-platform for a long time</a>;</li>
<li>it’s responsive;</li>
<li>it’s tried and tested;</li>
<li>it brings some kind of interoperability since it has been used by a lot of Reading Systems and authors have been designing against them.</li>
</ul>
<section id="default" class="level3">
<h3 class="sigil_not_in_toc">Default</h3>
<p>Pagination is responsive by default, which means it is using relative values in order to adapt layout to the viewport and the current font size.</p>
<p>We’ve chosen this approach since it appears setting everything in pixels is more likely to create rounding errors and rendering issues (e.g. cut-off text) than letting the rendering engine deal with relative units on its own.</p>
<p>The responsive design provides other benefits. For instance, if the reader is using an iPad in landscape mode and sets a bigger font size, the two-column view will automatically switch to a single-page view if needed.</p>
<p>You can also limit line-length by setting a <code>max-width</code> for <code>body</code>.</p>
<p>Please note a user setting for the number of columns has been designed so that users can set the layout as they wish.</p>
</section>
<section id="the-rs-owns-root-and-part-of-body" class="level3">
<h3 class="sigil_not_in_toc">The RS owns :root and part of body</h3>
<p>Since we must inject contents and columns are implemented at the <code>:root</code> level (i.e. <code>html</code>), the Reading System owns the entire styling for this selector.</p>
<p>Font size is an important metric since the responsive design relies entirely on <code>rem</code> (root <code>em</code>) so this style must be enforced by any means necessary.</p>
<p>For <code>body</code>, we own:</p>
<ul>
<li><code>overflow</code>;</li>
<li>sizing: <code>(min-|max-)width</code>, <code>(min-|max-)height</code>, <code>box-sizing</code>;</li>
<li>spacing: <code>margin</code> and <code>padding</code>.</li>
</ul>
<p>You can control horizontal margins in several ways:</p>
<ol>
<li>using <code>column-gap</code> and <code>padding</code> for <code>:root</code>;</li>
<li>using <code>column-gap</code> and <code>margin</code> for the web view/chrome view/iframe;</li>
<li>using <code>padding</code> for <code>:root</code> and/or <code>body</code>.</li>
</ol>
<p>Please note that when using <code>padding</code>, you must take it into account when sizing <code>:root</code> and/or <code>body</code>. Their widths contain the padding set for the element.</p>
<section id="the-pagination-model" class="level3">
<h3 class="sigil_not_in_toc">The pagination model</h3>
<p>This is the model you’re dealing with. It’s been simplified in version 2 in order to be more reliable.</p>
<figure class="fullbleed">
<img src="../Images/Page-Model.jpg" alt="The single page model relies on the column width of the :root element. Line-length is constrained by the max-width of the body element, including its padding. Finally an auto margin centers the content."/>
</figure>
<p>Page gutters are part of <code>body</code> (<code>--RS__pageGutter</code>), hence <code>--USER__lineLength</code> (or <code>--RS__defaultLineLength</code> if no user preference is set). Contents are centered in <code>:root</code> using the <code>auto</code> value for <code>body</code> margins.</p>
<p>By default, <code>--RS__pageGutter</code> is set to <code>0</code>. You can set it as you wish, but take into account it will substract from <code>--USER__lineLength</code>. </p>
</section>
<section id="variables-you-can-set" class="level4">
<h4 class="sigil_not_in_toc">Variables you can set</h4>
<p>Please note those variables’ value can be redefined using media queries. You don’t need to redeclare entire declarations.</p>
<hr/>
<pre><code>--RS__colWidth</code></pre>
<p>The optimal column’s width. We set it to <code>100vw</code> (<code>100vh</code> in vertical writing) for a single-column for Safari – otherwise it won’t fragment content, and <code>auto</code> for multiple so that the column-count can be prioritized.</p>
<hr/>
<pre><code>--RS__colCount</code></pre>
<p>The optimal number of columns (depending on the columns’ width).</p>
<hr/>
<pre><code>--RS__colGap</code></pre>
<p>The gap between columns.</p>
<p>You must account for this gap when scrolling.</p>
<hr/>
<pre><code>--RS__pageGutter</code></pre>
<p>The inline (horizontal by default, vertical in vertical-writing) page margins.</p>
<hr/>
<pre><code>--RS__defaultLineLength</code></pre>
<p>The default line-length when none is set by the user. It represents the <code>max-width</code> of the <code>body</code> element and is <code>100%</code> by default so that it does not conflict with the the zoom factor.</p>
<hr/>
<pre><code>--USER__lineLength</code></pre>
<p>The line-length set by the user. It can be set in any unit CSS property <code>max-width</code> accepts.</p>
</section>
</section>
<section id="right-to-left-progression" class="level3">
<h3 class="sigil_not_in_toc">Right-to-left progression</h3>
<p>The pagination model will take care of itself if the correct <code>dir</code> attribute is set on <code>html</code> and <code>body</code>.</p>
<p>In other words, if <code>dir="rtl"</code> is set for both elements, the column-progression will be automatically reversed.</p>
<section id="when-to-use-the-right-to-left-progression" class="level4">
<h4 class="sigil_not_in_toc">When to use the Right-to-left progression</h4>
<p>What implementers need to do:</p>
<ol>
<li>check the <code>page-progression-direction</code> for the <code>spine</code> item;</li>
<li>check the language – do not forget there can be multiple <code><dc:language></code> items;</li>
<li>load specific styles for RTL scripts;</li>
<li>append <code>xml:lang</code> and/or <code>lang</code> attribute if it’s missing in XHTML documents;</li>
<li>append <code>dir="rtl"</code> attributes if they’re missing for both <code>html</code> and <code>body</code> in XHTML documents;</li>
<li>load specific fonts’ lists for user settings, based on the primary language of the publication;</li>
<li>add/remove specific user settings, based on the primary language of the publication;</li>
<li>Apply the correct <code>page-progression-direction</code> (in RTL, next resource is on the left, previous is on the right);</li>
<li>change the direction of the toc and at least some pieces of user settings (e.g. <code>text-align</code>).</li>
</ol>
<p>The current implementation is limited to the following combinations:</p>
<table>
<thead>
<tr class="header">
<th>
Language
</th>
<th>
IANA tag
</th>
<th>
page-progression-direction
</th>
<th>
dir attribute
</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>
Arabic
</td>
<td>
ar
</td>
<td>
RTL
</td>
<td>
rtl
</td>
</tr>
<tr class="even">
<td>
Farsi (Persian)
</td>
<td>
fa
</td>
<td>
RTL
</td>
<td>
rtl
</td>
</tr>
<tr class="odd">
<td>
Hebrew
</td>
<td>
he
</td>
<td>
RTL
</td>
<td>
rtl
</td>
</tr>
</tbody>
</table>
<p><a href="https://www.iana.org/assignments/language-subtag-registry/language-subtag-registry">IANA Language Subtag registery</a>.</p>
<p>We may add others at some point in the future. Please feel free to report the languages or scripts missing in this mapping. Please bear in mind a list of default (preferably system) fonts will greatly help to add support for those languages and scripts. See <a href="../Text/Section-009.xhtml">Default Fonts</a>.</p>
<p>Test files can be retrieved from <a href="https://raw.githubusercontent.com/readium/css/develop/docs/i18n-samples/root.atom">the Readium CSS’ i18n-samples OPDS feed</a>.</p>
</section>
<section id="be-cautious-the-direction-propagates" class="level4">
<h4 class="sigil_not_in_toc">Be cautious, the direction propagates</h4>
<p>As explicitly stated in <a href="https://www.w3.org/TR/css-writing-modes-3/#principal-flow">CSS Writing Modes Level 3</a>:</p>
<blockquote>
<p>As a special case for handling HTML documents, if the <code>:root</code> element has a <code><body></code> child element, the principal writing mode is instead taken from the values of <code>writing-mode</code> and <code>direction</code> on the first such child element instead of taken from the root element.</p>
</blockquote>
<p>What this means is that the <code>dir</code> attribute (or the <code>direction</code> CSS property) set for <code>body</code> will override the one set for <code>html</code>. Unlike most other CSS properties, which don’t impact the parent element, the <code>dir</code> attribute (or the <code>direction</code> CSS property) propagates in this very specific case:</p>
<pre><code><html dir="ltr">
<body dir="rtl">
<!-- dir="rtl" should be used. --></code></pre>
<pre><code>html {
direction: ltr;
}
body {
direction: rtl;
/* rtl propagates to html and overrides ltr.
You can think of it as a JS event bubbling up
if that makes more sense. */
}</code></pre>
<p>We MUST consequently force the direction for all documents in the publication, and can’t manage <code>ltr</code> documents in a <code>rtl</code> publication.</p>
<p>Note: While this isn’t necessarily the case in practice, in Blink, Gecko/Quantum and Webkit, and you can emulate a reversed column-progression for <code>ltr</code> documents in a <code>rtl</code> publication, this behavior may change in the future.</p>
</section>
</section>
<section id="the-pagination-model-for-vertical-writing-modes" class="level3">
<h3 class="sigil_not_in_toc">The pagination model for vertical writing modes</h3>
<p>When publications are in Chinese, Japanese, Korean, and Mongolian, and laid out with a <code>vertical-*</code> writing mode, we must switch to a different model.</p>
<p>Indeed, columns are automatically laid out on the <code>y-axis</code> (vertical) with such writing modes, and <a href="https://www.w3.org/TR/css-writing-modes-3/#changes-201512">the behavior of multi-column in orthogonal flows has been deferred to CSS Writing Modes Level 4</a>. This means we must stick to a single column, and can’t support several columns – they are stacked on top of one another, which is not what is expected.</p>
<p>This also implies the scroll progression is vertical, hence horizontal navigation/swipes have to be re-mapped on this <code>y-axis</code>. You may also want to disable animations so that it doesn’t feel disorienting to users.</p>
<p>We consequently use a “Fragmented Model”, as it differs significantly from the “Pagination Model”, especially the column-axis.</p>
<figure class="fullbleed">
<img src="../Images/Fragmented-Model.jpg" alt="The fragmented Model is kind of a superset of the single page model in the vertical direction, with extra padding added to the root element for extra horizontal gutters."/>
</figure>
<p>One can think of the fragmented model as the single page model rotated 90% clockwise.</p>
<p>Due to the limitations listed above, implementers may want to use their own model. It is not uncommon to handle vertical writing pagination programmatically, as it can be done relatively easily and efficiently thanks to characters being (mostly) monospace e.g. scrolling the viewport by an offset based on these characters.</p>
<p>Since pagination is the default view, if you don’t want to use this model and implement yours, you can set <code>--RS__disablePagination: readium-noVerticalPagination-on</code> on the <code>:root</code> (<code>html</code>) element.</p>
<section id="when-to-use-the-fragmented-model" class="level4">
<h4 class="sigil_not_in_toc">When to use the fragmented model</h4>
<p>What implementers need to do:</p>
<ol>
<li>check the <code>page-progression-direction</code> for the <code>spine</code> item;</li>
<li>check the language – do not forget there can be multiple <code><dc:language></code> items;</li>
<li>load the specific styles for CJK if needed;</li>
<li>append <code>xml:lang</code> and/or <code>lang</code> attribute if it’s missing in XHTML documents;</li>
<li>load specific fonts’ lists for user settings, based on the primary language of the publication;</li>
<li>add/remove specific user settings, based on the primary language of the publication;</li>
<li>Apply the correct page-progression-direction (in RTL, next resource is on the left, previous is on the right).</li>
</ol>
<p>Here is the correct mapping for combinations resulting in the <code>vertical-*</code> writing mode:</p>
<table>
<thead>
<tr class="header">
<th>
Language
</th>
<th>
IANA tag
</th>
<th>
page-progression-direction
</th>
<th>
Writing-mode
</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>
Chinese
</td>
<td>
zh
</td>
<td>
RTL
</td>
<td>
vertical-rl
</td>
</tr>
<tr class="even">
<td>
Chinese (Traditional)
</td>
<td>
zh-Hant
</td>
<td>
RTL
</td>
<td>
vertical-rl
</td>
</tr>
<tr class="odd">
<td>
Chinese (Taiwan)
</td>
<td>
zh-TW
</td>
<td>
RTL
</td>
<td>
vertical-rl
</td>
</tr>
<tr class="even">
<td>
Chinese (Hong Kong)
</td>
<td>
zh-HK
</td>
<td>
RTL
</td>
<td>
vertical-rl
</td>
</tr>
<tr class="odd">
<td>
Korean
</td>
<td>
ko
</td>
<td>
RTL
</td>
<td>
vertical-rl
</td>
</tr>
<tr class="even">
<td>
Japanese
</td>
<td>
ja
</td>
<td>
RTL
</td>
<td>
vertical-rl
</td>
</tr>
<tr class="odd">
<td>
Mongolian
</td>
<td>
mn-Mong
</td>
<td>
LTR / Default / None
</td>
<td>
vertical-lr
</td>
</tr>
</tbody>
</table>
<p><a href="https://www.iana.org/assignments/language-subtag-registry/language-subtag-registry">IANA Language Subtag registery</a>.</p>
<p>Test files can be retrieved from <a href="https://raw.githubusercontent.com/readium/css/develop/docs/i18n-samples/root.atom">the Readium CSS’ i18n-samples OPDS feed</a>.</p>
</section>
<section id="when-not-to-use-the-fragmented-model" class="level4">
<h4 class="sigil_not_in_toc">When not to use the fragmented model</h4>
<p>If a publication doesn’t need to be laid out in a <code>vertical-*</code> writing mode, the default pagination model must be used.</p>
<p>There are still specific styles for CJK Horizontal to load though.</p>
<p>Here is the correct mapping for combinations resulting in the <code>horizontal-tb</code> writing mode:</p>
<table>
<thead>
<tr class="header">
<th>
Language
</th>
<th>
IANA tag
</th>
<th>
page-progression-direction
</th>
<th>
Writing-mode
</th>
</tr>
</thead>
<tbody>
<tr class="odd">
<td>
Chinese
</td>
<td>
zh
</td>
<td>
LTR / Default / None
</td>
<td>
horizontal-tb
</td>
</tr>
<tr class="even">
<td>
Chinese (Simplified)
</td>
<td>
zh-Hans
</td>
<td>
LTR / Default / None
</td>
<td>
horizontal-tb
</td>
</tr>
<tr class="odd">
<td>
Chinese (Taiwan)
</td>
<td>
zh-TW
</td>
<td>
LTR / Default / None
</td>
<td>
horizontal-tb
</td>
</tr>
<tr class="even">
<td>
Chinese (Hong Kong)
</td>
<td>
zh-HK
</td>
<td>
LTR / Default / None
</td>
<td>
horizontal-tb
</td>
</tr>
<tr class="odd">
<td>
Korean
</td>
<td>
ko
</td>
<td>
LTR / Default / None
</td>
<td>
horizontal-tb
</td>
</tr>
<tr class="even">
<td>
Japanese
</td>
<td>
ja
</td>
<td>
LTR / Default / None
</td>
<td>
horizontal-tb
</td>
</tr>
<tr class="odd">
<td>
Mongolian
</td>
<td>
mn-Cyrl
</td>
<td>
LTR / Default / None
</td>
<td>
horizontal-tb
</td>
</tr>
</tbody>
</table>
<p><a href="https://www.iana.org/assignments/language-subtag-registry/language-subtag-registry">IANA Language Subtag registery</a>.</p>
</section>
<section id="be-cautious-the-writing-mode-css-property-propagates" class="level4">
<h4 class="sigil_not_in_toc">Be cautious, the writing-mode CSS property propagates</h4>
<p>As explicitly stated in <a href="https://www.w3.org/TR/css-writing-modes-3/#principal-flow">CSS Writing Modes Level 3</a>:</p>
<blockquote>
<p>As a special case for handling HTML documents, if the <code>:root</code> element has a <code><body></code> child element, the principal writing mode is instead taken from the values of <code>writing-mode</code> and <code>direction</code> on the first such child element instead of taken from the root element.</p>
</blockquote>
<p>What this means is that the <code>writing-mode</code> declared for <code>body</code> will override the one declared for <code>html</code>. Unlike most other CSS properties, which don’t impact the parent element, <code>writing-mode</code> propagates in this very specific case:</p>
<pre><code>html {
writing-mode: horizontal-tb;
}
body {
writing-mode: vertical-rl;
/* vertical-rl propagates to html and overrides horizontal-tb.
You can think of it as a JS event bubbling up
if that makes more sense. */
}</code></pre>
<p>We MUST consequently force the <code>writing-mode</code> for all documents in the publication, and can’t manage <code>horizontal-tb</code> documents in a <code>vertical-rl</code> publication.</p>
</section>
</section>
<section id="patch-and-safeguards" class="level3">
<h3 class="sigil_not_in_toc">Patch and safeguards</h3>
<p>We’ve designed two extras for pagination:</p>
<ol>
<li>a patch for HTML5 Suggested Rendering, which takes care of paged media;</li>
<li>safeguards, which make sure some elements will be managed as expected by authors in columns.</li>
</ol>
<section id="patch" class="level4">
<h4 class="sigil_not_in_toc">Patch</h4>
<p>The HTML5 patch deals with:</p>
<ul>
<li>fragmentation (<code>widows</code>, <code>orphans</code> and <code>page-break</code>);</li>
<li>hyphenation;</li>
<li>open type features;</li>
<li>horizontal margins (pixels have been converted to %);</li>
<li>normalization of <code>abbr</code> and <code>wbr</code>.</li>
</ul>
<p>You can use it with or without pagination, it should not make any difference.</p>
</section>
<section id="safeguards" class="level4">
<h4 class="sigil_not_in_toc">Safeguards</h4>
<p>Safeguards deal with:</p>
<ul>
<li>media sizing (e.g. <code>img</code>, <code>svg</code>, <code>audio</code>, <code>video</code>);</li>
<li>word wrap for long strings (headings and links);</li>
<li>large table’s overflow.</li>
</ul>
<p>Once again, you can use it with or without pagination, it should not make any difference.</p>
<section id="variables-you-can-set-1" class="level5">
<h5 class="sigil_not_in_toc">Variables you can set</h5>
<hr/>
<pre><code>--RS__maxMediaWidth</code></pre>
<p>The <code>max-width</code> for media elements i.e. <code>img</code>, <code>svg</code>, <code>audio</code> and <code>video</code>.</p>
<hr/>
<pre><code>--RS__maxMediaHeight</code></pre>
<p>The <code>max-height</code> for media elements i.e. <code>img</code>, <code>svg</code>, <code>audio</code> and <code>video</code>.</p>
<hr/>
<pre><code>--RS__boxSizingMedia</code></pre>
<p>The box model (<code>box-sizing</code>) you want to use for media elements.</p>
<hr/>
<pre><code>--RS__boxSizingTable</code></pre>
<p>The box model (<code>box-sizing</code>) you want to use for tables.</p>
</section>
</section>
</section>
</section>
</section>
</body>
</html>