-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Expand file tree
/
Copy pathstructure.scss
More file actions
83 lines (63 loc) · 1.64 KB
/
structure.scss
File metadata and controls
83 lines (63 loc) · 1.64 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
@import "../themes/ionic.globals";
@import "../themes/ionic.mixins";
// Structure
// --------------------------------------------------
// Adds structural css to the native html elements
* {
box-sizing: border-box;
-webkit-tap-highlight-color: rgba(0, 0, 0, 0);
-webkit-tap-highlight-color: transparent;
-webkit-touch-callout: none;
}
html {
width: 100%;
height: 100%;
-webkit-text-size-adjust: 100%;
text-size-adjust: 100%;
}
html.ion-ce body {
display: block;
}
html.plt-pwa {
height: 100vh;
}
body {
@include font-smoothing();
@include margin(0);
@include padding(0);
position: fixed;
width: 100%;
max-width: 100%;
height: 100%;
max-height: 100%;
/**
* Because body has position: fixed,
* it should be promoted to its own
* layer.
*
* WebKit does not always promote
* the body to its own layer on page
* load in Ionic apps. Once scrolling on
* ion-content starts, WebKit will promote
* body. Unfortunately, this causes a re-paint
* which results in scrolling being halted
* until the next user gesture.
*
* This impacts the Custom Elements build.
* The lazy loaded build causes the browser to
* re-paint during hydration which causes WebKit
* to promote body to its own layer.
* In the CE Build, this hydration does not
* happen, so the additional re-paint does not occur.
*/
transform: translateZ(0);
text-rendering: optimizeLegibility;
overflow: hidden;
touch-action: manipulation;
-webkit-user-drag: none;
-ms-content-zooming: none;
word-wrap: break-word;
overscroll-behavior-y: none;
-webkit-text-size-adjust: none;
text-size-adjust: none;
}