keystone_ui-preferences 0.10.1 → 0.10.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: d49104296c4ab87a70762c5e05c9257d39320610dc7e412f3447b3e626c6935f
|
|
4
|
+
data.tar.gz: 9048db5cfc549e83efc5b53a62772411ce4e84ce3dd6adbf9fcbb39f299c6c0e
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: f894ce79ae1e17c6f136661125edb9f78532ef7336d5a9df09afe29905929bdc1fe6bae5b0973468461bbf3d824237066e1e03efdbc98543a3942e72b905827a
|
|
7
|
+
data.tar.gz: e41c53bd16beed10b80392162093881b3f53cf27d96c7a6f1bce56c97623039aa16a5971e46cc3570bd4e36f94c253207334dc4de6cea2f3fea79b29b09c7ce3
|
data/README.md
CHANGED
|
@@ -224,7 +224,7 @@ The gem gives keystone_ui the mode through keystone_ui's theme mode supplier, so
|
|
|
224
224
|
<html <%= keystone_theme_attributes %>>
|
|
225
225
|
```
|
|
226
226
|
|
|
227
|
-
A visitor who is not signed in gets `default_mode`. A choice made with keystone_ui's theme toggle is kept in a cookie and wins over the saved mode in that browser. Saving in the appearance section clears that cookie, so the saved mode shows on the next page. The clearing runs in settings_hub's `after_settings_change` hook, which the `ComponentPreferences` concern defines, so an app that defines its own `after_settings_change` calls `super` from it.
|
|
227
|
+
A visitor who is not signed in gets `default_mode`. A choice made with keystone_ui's theme toggle is kept in a cookie and wins over the saved mode in that browser. `keystone_theme_mode` returns the same choice, so a layout that marks its page dark from it follows the toggle too. Saving in the appearance section clears that cookie, so the saved mode shows on the next page. The clearing runs in settings_hub's `after_settings_change` hook, which the `ComponentPreferences` concern defines, so an app that defines its own `after_settings_change` calls `super` from it.
|
|
228
228
|
|
|
229
229
|
## Look
|
|
230
230
|
|