Hallo.gent issueshttps://source.small-tech.org/indienet/hallo-gent/-/issues2018-05-02T07:09:11Zhttps://source.small-tech.org/indienet/hallo-gent/-/issues/141separate uploads from static2018-05-02T07:09:11ZFraukeseparate uploads from statichttps://source.small-tech.org/indienet/hallo-gent/-/issues/140Localisation defaults to Belgian Dutch when language is English in Safari on Mac2018-04-26T11:42:41ZAral BalkanLocalisation defaults to Belgian Dutch when language is English in Safari on MacOn Safari, with region set to "United Kingdom" (English (U.K.)) in Settings, it displays as Belgian Dutch.
navigator.language is `"en-GB"`
On Firefox, all of the following language settings (in Firefox preferences) work: English (`"en"...On Safari, with region set to "United Kingdom" (English (U.K.)) in Settings, it displays as Belgian Dutch.
navigator.language is `"en-GB"`
On Firefox, all of the following language settings (in Firefox preferences) work: English (`"en"`), US English (`"en-US"`), and British English (`"en-GB"`).
Console output when running in Safari:
```
Hallo.gent running on http://localhost:8080
[vue-i18n] Fall back to translate the keypath 'title' with 'nl' locale.
[vue-i18n] Fall back to translate the keypath 'title' with 'nl' locale.
[vue-i18n] Fall back to translate the keypath 'title' with 'nl' locale.
[vue-i18n] Fall back to translate the keypath 'title' with 'nl' locale.
[vue-i18n] Fall back to translate the keypath 'subtitle' with 'nl' locale.
[vue-i18n] Fall back to translate the keypath 'subtitle' with 'nl' locale.
[vue-i18n] Fall back to translate the keypath 'subtitle' with 'nl' locale.
[vue-i18n] Fall back to translate the keypath 'nav.me' with 'nl' locale.
[vue-i18n] Fall back to translate the keypath 'nav.everyone' with 'nl' locale.
[vue-i18n] Fall back to translate the keypath 'nav.search' with 'nl' locale.
[vue-i18n] Fall back to translate the keypath 'nav.settings' with 'nl' locale.
{ statusCode: 404,
path: '/_nuxt/a38811e382d02f911457.hot-update.json',
message: 'This page could not be found' }
[vue-i18n] Fall back to translate the keypath 'title' with 'nl' locale.
[vue-i18n] Fall back to translate the keypath 'title' with 'nl' locale.
[vue-i18n] Fall back to translate the keypath 'title' with 'nl' locale.
[vue-i18n] Fall back to translate the keypath 'title' with 'nl' locale.
[vue-i18n] Fall back to translate the keypath 'subtitle' with 'nl' locale.
[vue-i18n] Fall back to translate the keypath 'subtitle' with 'nl' locale.
[vue-i18n] Fall back to translate the keypath 'subtitle' with 'nl' locale.
[vue-i18n] Fall back to translate the keypath 'nav.me' with 'nl' locale.
[vue-i18n] Fall back to translate the keypath 'nav.everyone' with 'nl' locale.
[vue-i18n] Fall back to translate the keypath 'nav.search' with 'nl' locale.
[vue-i18n] Fall back to translate the keypath 'nav.settings' with 'nl' locale.
[vue-i18n] Fall back to translate the keypath 'errors.domain.pattern' with 'nl' locale.
[vue-i18n] Fall back to translate the keypath 'questions' with 'nl' locale.
[vue-i18n] Fall back to translate the keypath 'title' with 'nl' locale.
[vue-i18n] Fall back to translate the keypath 'title' with 'nl' locale.
[vue-i18n] Fall back to translate the keypath 'title' with 'nl' locale.
[vue-i18n] Fall back to translate the keypath 'title' with 'nl' locale.
[vue-i18n] Fall back to translate the keypath 'subtitle' with 'nl' locale.
[vue-i18n] Fall back to translate the keypath 'subtitle' with 'nl' locale.
[vue-i18n] Fall back to translate the keypath 'subtitle' with 'nl' locale.
[vue-i18n] Fall back to translate the keypath 'nav.me' with 'nl' locale.
[vue-i18n] Fall back to translate the keypath 'nav.everyone' with 'nl' locale.
[vue-i18n] Fall back to translate the keypath 'nav.search' with 'nl' locale.
[vue-i18n] Fall back to translate the keypath 'nav.settings' with 'nl' locale.
[vue-i18n] Fall back to translate the keypath 'errors.domain.pattern' with 'nl' locale.
[vue-i18n] Fall back to translate the keypath 'questions' with 'nl' locale.
[vue-i18n] Fall back to translate the keypath 'title' with 'nl' locale.
[vue-i18n] Fall back to translate the keypath 'title' with 'nl' locale.
[vue-i18n] Fall back to translate the keypath 'title' with 'nl' locale.
[vue-i18n] Fall back to translate the keypath 'title' with 'nl' locale.
[vue-i18n] Fall back to translate the keypath 'subtitle' with 'nl' locale.
[vue-i18n] Fall back to translate the keypath 'subtitle' with 'nl' locale.
[vue-i18n] Fall back to translate the keypath 'subtitle' with 'nl' locale.
[vue-i18n] Fall back to translate the keypath 'nav.me' with 'nl' locale.
[vue-i18n] Fall back to translate the keypath 'nav.everyone' with 'nl' locale.
[vue-i18n] Fall back to translate the keypath 'nav.search' with 'nl' locale.
[vue-i18n] Fall back to translate the keypath 'nav.settings' with 'nl' locale.
[vue-i18n] Fall back to translate the keypath 'errors.domain.pattern' with 'nl' locale.
[vue-i18n] Fall back to translate the keypath 'questions' with 'nl' locale.
[vue-i18n] Fall back to translate the keypath 'title' with 'nl' locale.
[vue-i18n] Fall back to translate the keypath 'title' with 'nl' locale.
[vue-i18n] Fall back to translate the keypath 'title' with 'nl' locale.
[vue-i18n] Fall back to translate the keypath 'title' with 'nl' locale.
[vue-i18n] Fall back to translate the keypath 'subtitle' with 'nl' locale.
[vue-i18n] Fall back to translate the keypath 'subtitle' with 'nl' locale.
[vue-i18n] Fall back to translate the keypath 'subtitle' with 'nl' locale.
[vue-i18n] Fall back to translate the keypath 'nav.me' with 'nl' locale.
[vue-i18n] Fall back to translate the keypath 'nav.everyone' with 'nl' locale.
[vue-i18n] Fall back to translate the keypath 'nav.search' with 'nl' locale.
[vue-i18n] Fall back to translate the keypath 'nav.settings' with 'nl' locale.
[vue-i18n] Fall back to translate the keypath 'errors.domain.pattern' with 'nl' locale.
[vue-i18n] Fall back to translate the keypath 'questions' with 'nl' locale.
```https://source.small-tech.org/indienet/hallo-gent/-/issues/139Refactor account code creation/population to allow codes to be created indepe...2018-04-26T08:46:48ZAral BalkanRefactor account code creation/population to allow codes to be created independently of the deploymentIn the deployment environment, it is not possible (due to our choice of an in-process, single-connection database, LevelDB), to run the current account generation script while the app itself is running.
It is also more flexible to separ...In the deployment environment, it is not possible (due to our choice of an in-process, single-connection database, LevelDB), to run the current account generation script while the app itself is running.
It is also more flexible to separate the app and the account code creation so that the account code creation script can exist independently.
## How it should work
1. On any machine, someone runs the account code script and generates the codes, which are saved to a JSON file in a directory with an index suffix: e.g., _codes-0.json_. Successive runs of the script on the same machine cause the counter to increase. Old codes are not deleted. (e.g., _codes-1.json, codes-2.json_, etc.)
2. The codes directory is copied to the app (e.g., to ~/.hallo.gent/codes)
3. On startup, the app loads in all the files in that directory and checks to see if there are any new files that are not in its database. If there are, it populates the database with the new codes and then continues the rest of the startup process.Aral BalkanAral Balkanhttps://source.small-tech.org/indienet/hallo-gent/-/issues/138Get is-correct-0000, etc., hardcoded codes to work in production2018-04-27T07:26:44ZAral BalkanGet is-correct-0000, etc., hardcoded codes to work in productionUntil we have an actual Magic Website Factory implementation, the deployed version of Hallo.gent is going to be a demonstration of how the system is expected to work. As such, the hardcoded testing codes should be made to work in the dep...Until we have an actual Magic Website Factory implementation, the deployed version of Hallo.gent is going to be a demonstration of how the system is expected to work. As such, the hardcoded testing codes should be made to work in the deployed environment for the time being.
Also document in the code that this has to be reverted back once an actual implementation is live (and keep the code for that conditional commented out in there so we don’t have to hunt it down and do that work again in the future).https://source.small-tech.org/indienet/hallo-gent/-/issues/137Settings/Localisation: On changing language from English, name/Bio text and p...2018-04-25T12:48:14ZLaura KalbagSettings/Localisation: On changing language from English, name/Bio text and placeholder text is not localised to Belgian DutchWhen I change the language to Nederlands, the Name and Bio placeholders remain in English:
![Screen_Shot_2018-04-25_at_13.14.11](/uploads/e7d89e9d2c99a99454ae590fb355f6c2/Screen_Shot_2018-04-25_at_13.14.11.png)
Also the default name/bi...When I change the language to Nederlands, the Name and Bio placeholders remain in English:
![Screen_Shot_2018-04-25_at_13.14.11](/uploads/e7d89e9d2c99a99454ae590fb355f6c2/Screen_Shot_2018-04-25_at_13.14.11.png)
Also the default name/bio in the header:
![Screen_Shot_2018-04-25_at_13.16.35](/uploads/4f36689136ca9485310318b638437bbe/Screen_Shot_2018-04-25_at_13.16.35.png)
If you started the process in Belgian Dutch, the placeholders and text is localised :smile:Laura KalbagLaura Kalbaghttps://source.small-tech.org/indienet/hallo-gent/-/issues/136Settings/Localisation: Theme colour names are not localised to Belgian Dutch2018-04-25T12:28:21ZLaura KalbagSettings/Localisation: Theme colour names are not localised to Belgian DutchWhen I change the language to Belgian Dutch, and use a screen reader/keyboard navigation to access the colour swatches, the swatch names are still in English
![Screen_Shot_2018-04-25_at_13.09.05](/uploads/a46782b75b1de2e30e82f9549cd8a3...When I change the language to Belgian Dutch, and use a screen reader/keyboard navigation to access the colour swatches, the swatch names are still in English
![Screen_Shot_2018-04-25_at_13.09.05](/uploads/a46782b75b1de2e30e82f9549cd8a30c/Screen_Shot_2018-04-25_at_13.09.05.png)FraukeFraukehttps://source.small-tech.org/indienet/hallo-gent/-/issues/135Setup: Validation needs to be handled in a consistent way across form inputs2018-04-25T13:38:52ZLaura KalbagSetup: Validation needs to be handled in a consistent way across form inputsOn the input for the code, when you enter anything that isn’t the correct code, the only feedback you get is the subtle red outline.
![Screen_Shot_2018-04-25_at_12.52.12](/uploads/98d15f77b4ceb8499da8d8702c75ad91/Screen_Shot_2018-04-25_...On the input for the code, when you enter anything that isn’t the correct code, the only feedback you get is the subtle red outline.
![Screen_Shot_2018-04-25_at_12.52.12](/uploads/98d15f77b4ceb8499da8d8702c75ad91/Screen_Shot_2018-04-25_at_12.52.12.png)
Occasionally, VoiceOver will pick up the ‘The code isn’t in the right format’ and display it in a bubble above the input (I had to hold down Enter and it would flicker into view, however it didn’t seem to be there for long enough for VoiceOver to read it—despite what the screenshot shows!)
![Screen_Shot_2018-04-25_at_12.57.08](/uploads/4e7a361b639e8a5ae8928039fd32db30/Screen_Shot_2018-04-25_at_12.57.08.png)
Using HTML5 form validation, we can rely on good browser defaults (including accessibility for non-visual feedback), especially [as it is widely-supported](https://caniuse.com/#search=form%20validation). As a general rule, it’s best to wait for form submission to show errors, as giving feedback on each individual character typed is an experience nightmare, particularly for a person using a screenreader. In Inclusive Design Patterns, Heydon Pickering recommends checking the whole form for validation on submit (while suppressing actual submission) and then perhaps providing live validation on the fields that need correcting (as the person using the form definitely needs assistance at that point, and will expect it.)
I think it’s worthwhile considering the domain name input as a separate treatment from standard validation. Because it’s not a question of whether the person has entered something correctly/incorrecting, it’s a check on our end. Currently the input for the domain name provides validation feedback based upon matching a correct domain name pattern, but we will still need to validate against actual domain name availability. This is probably more useful to do live (maybe on pause/delay), so the person gets live feedback, and doesn’t have to submit and wait for feedback.
Any other thoughts welcome!Laura KalbagLaura Kalbaghttps://source.small-tech.org/indienet/hallo-gent/-/issues/134Settings: Safari shows big gap to right of layout2018-04-25T07:53:43ZLaura KalbagSettings: Safari shows big gap to right of layoutIn Safari, there’s a big gap on the right side of the Settings layout:
![Screen_Shot_2018-04-24_at_15.35.45](/uploads/eeb08e9c5aa633f9dfd6d34a69156ebf/Screen_Shot_2018-04-24_at_15.35.45.png)
It looks like the culprit is the radio butto...In Safari, there’s a big gap on the right side of the Settings layout:
![Screen_Shot_2018-04-24_at_15.35.45](/uploads/eeb08e9c5aa633f9dfd6d34a69156ebf/Screen_Shot_2018-04-24_at_15.35.45.png)
It looks like the culprit is the radio buttons displaying at 100% width:
![Screen_Shot_2018-04-24_at_15.34.32](/uploads/02a260c5a2c828e92940af19ee807b62/Screen_Shot_2018-04-24_at_15.34.32.png)
This may be fixed using `overflow: hidden;` on one of the containing elements, but I don’t want to go slinging CSS like this around when it may have negative consequences, so I’ll leave that to you… :wink:https://source.small-tech.org/indienet/hallo-gent/-/issues/133Settings: Colour picker swatches are not selectable and are displaying in col...2018-04-25T07:53:36ZLaura KalbagSettings: Colour picker swatches are not selectable and are displaying in column in Chrome![Screen_Shot_2018-04-24_at_15.24.59](/uploads/415f1270f49b69dcb83ef5cc195f5b03/Screen_Shot_2018-04-24_at_15.24.59.png)
- In Safari, hover styles work, but swatches are not selectable using mouse or keyboard (so theme cannot change to r...![Screen_Shot_2018-04-24_at_15.24.59](/uploads/415f1270f49b69dcb83ef5cc195f5b03/Screen_Shot_2018-04-24_at_15.24.59.png)
- In Safari, hover styles work, but swatches are not selectable using mouse or keyboard (so theme cannot change to reflect selected swatch).
- In Chrome and Opera, hover styles work, swatches retain their selected state, but theme does not change to reflect selected swatch. Swatches also display in one column:
![Screen_Shot_2018-04-24_at_15.25.53](/uploads/0914feadab004f293b3f3d036b701df6/Screen_Shot_2018-04-24_at_15.25.53.png)
- In Firefox, the swatches work as intended. (And the little save dialog is cute!)https://source.small-tech.org/indienet/hallo-gent/-/issues/132Deploy hallo.gent, test.magicwebsitefactory.gent, and available.gent2018-04-24T13:06:56ZAral BalkanDeploy hallo.gent, test.magicwebsitefactory.gent, and available.gent## Goals
* To be able to demonstrate publicly how Hallo.gent and Indie Site are meant to function
* To get us to incorporate deployment into our workflow and to be even more transparent in our development process by deploying the cu...## Goals
* To be able to demonstrate publicly how Hallo.gent and Indie Site are meant to function
* To get us to incorporate deployment into our workflow and to be even more transparent in our development process by deploying the current state of the tools regularly
* Use the Hallo.gent site to link to ongoing media coverage, etc., of the project and to have a site that people can visit when they hear about the project (since the name is also the domain name, it cannot be mentioned without the domain name also being mentioned. The last thing people who visit links to the project should see is a domain holding page).
## Deployment details
### Domains/DNS
* Domains registered via Combell.
* Nameservers hosted with Amazon Route 53.
### Hosting
We use a single OpenStack-based VPS instance at cloudscale.ch and virtual hosts to host all three components.
All domain and hosting costs are currently being covered by Ind.ie.
### Deployment system
Dokku (Heroku-like `git push` deploys via Docker).
Remotes (for configuring your working copies):
* hallo.gent: `git remote add deploy dokku@hallo.gent:hallo.gent`
* available.gent: (this should be added as a remote to Indie Site): `git remote add available.gent dokku@hallo.gent:available`
* test.magicwebsitefactory.gent: `git remote add deploy dokku@hallo.gent:magicwebsitefactory`
### TLS
Provided and automatically renewed by [Dokku Let’s Encrypt plugin](https://github.com/dokku/dokku-letsencrypt).Aral BalkanAral Balkanhttps://source.small-tech.org/indienet/hallo-gent/-/issues/131Bug: Firefox on Mac defaults to Belgian Dutch even when locale is English2018-04-25T08:58:26ZAral BalkanBug: Firefox on Mac defaults to Belgian Dutch even when locale is English## To reproduce
1. On a Mac, make sure your language settings are English:
![Screen_Shot_2018-04-24_at_12.17.46](/uploads/37791d66f58aaf9ad8ed810e1c795df4/Screen_Shot_2018-04-24_at_12.17.46.png)
2. Launch Hallo.gent in Firefox.
#...## To reproduce
1. On a Mac, make sure your language settings are English:
![Screen_Shot_2018-04-24_at_12.17.46](/uploads/37791d66f58aaf9ad8ed810e1c795df4/Screen_Shot_2018-04-24_at_12.17.46.png)
2. Launch Hallo.gent in Firefox.
## What should happen
Site should be in English
## What actually happens
Site is in Belgian Dutch
![Screen_Shot_2018-04-24_at_12.17.06](/uploads/a7b3f4c622cc5e1d091673d7a5d1fe25/Screen_Shot_2018-04-24_at_12.17.06.png)https://source.small-tech.org/indienet/hallo-gent/-/issues/130Bug: able to submit domain name even though Magic Website Factory is not avai...2018-04-25T09:00:38ZAral BalkanBug: able to submit domain name even though Magic Website Factory is not available## To reproduce
1. Run Hallo.gent without Magic Website Factory
2. Enter code `is-correct-0000`
3. Enter domain: `available`
See validation error:
![Screen_Shot_2018-04-24_at_11.52.43](/uploads/17640eb2a3105d1d4341b415cbe11541...## To reproduce
1. Run Hallo.gent without Magic Website Factory
2. Enter code `is-correct-0000`
3. Enter domain: `available`
See validation error:
![Screen_Shot_2018-04-24_at_11.52.43](/uploads/17640eb2a3105d1d4341b415cbe11541/Screen_Shot_2018-04-24_at_11.52.43.png)
4. Press Enter.
## What should happen
Nothing. Validation has failed and the Send button is disabled. The form should not submit.
## What does happen
The form submits and an error is shown:
![Screen_Shot_2018-04-24_at_11.52.48](/uploads/73b41a40c141e06a96a45c37f08fb721/Screen_Shot_2018-04-24_at_11.52.48.png)https://source.small-tech.org/indienet/hallo-gent/-/issues/129Ensure colour swatch choices do not allow for low contrast text/background co...2018-04-24T15:14:46ZLaura KalbagEnsure colour swatch choices do not allow for low contrast text/background colour combinationsLighter colours in the colour choices result in low contrast between the text and background:
![Screen_Shot_2018-04-23_at_14.59.16](/uploads/50325f9ad44ef380967b4246af1c9282/Screen_Shot_2018-04-23_at_14.59.16.png)
* [ ] **Make all col...Lighter colours in the colour choices result in low contrast between the text and background:
![Screen_Shot_2018-04-23_at_14.59.16](/uploads/50325f9ad44ef380967b4246af1c9282/Screen_Shot_2018-04-23_at_14.59.16.png)
* [ ] **Make all colour choices result in sufficient contrast between text and background**.
If people want to do white on grey, they can hack their own stylesheets to do that, but we can give everybody else inclusive defaults.
*Perhaps* we could have some variation in the colours across the theme to enhance accessibility without losing the vibrancy of the colours. E.g. when used behind text, the colour is darker; when used as a background, the colour is lighter; when used as an accent shape, the colour retains its vibrancy. So an evolution of the thinking going on here:
![Screen_Shot_2018-04-23_at_15.04.00](/uploads/f21b7ad8dc90abdbc76b908e1f2580bc/Screen_Shot_2018-04-23_at_15.04.00.png)
The values will need to be chosen based on both what is accessible, and what is aesthetically-pleasing. This will make the variables/CSS slightly more complicated, but I think it will be worthwhile. I don’t think we can get away with doing it programmatically (e.g. doing CSS pre-processor calculations to add more black) as it’s hard/impossible to achieve both accessible and aesthetically pleasing. (Trust me, I tried so hard to achieve this on my own site recently and gained a few more grey hairs!)
Also would be nice to have:
* [ ] **Profile description background be darker shade of chosen colour**, rather than black
This could contribute to the feel/accessibility created above. For example, black on yellow is pretty grim, but dark yellow on yellow is a little more pleasing:
![Screen_Shot_2018-04-23_at_15.07.37](/uploads/787f60484ffbae4cea91835446cfd5b5/Screen_Shot_2018-04-23_at_15.07.37.png) (with low-alpha black)
![Screen_Shot_2018-04-23_at_15.09.44](/uploads/1a6ec5f805364b7f202bc0853e0a34d7/Screen_Shot_2018-04-23_at_15.09.44.png) (with low-alpha dark orange yellow)
![Screen_Shot_2018-04-23_at_15.09.56](/uploads/556dd7273734d0e52fa82529d2a8cdc3/Screen_Shot_2018-04-23_at_15.09.56.png) (with low-alpha dark orange yellow)
* [ ] **Hallobot background reflect chosen colour**
* [ ] **Default avatar reflect chosen colour** (on occasion that a person chooses a colour but doesn’t upload a profile image)
Thoughts on this: Maybe the Hallobot background should actually be the Stad Gent brand/default colour, as the Hallobot is not representative of the individual changing the settings (whereas the default avatar is…)?Laura KalbagLaura Kalbaghttps://source.small-tech.org/indienet/hallo-gent/-/issues/128Handle disabled states better2018-04-23T13:53:40ZLaura KalbagHandle disabled states betterCurrently, the disabled states could create difficulties from a usability and accessibility perspective in terms of:
- Pale grey text is too low contrast for many people with visual difficulties
- Darker grey text (text of a higher cont...Currently, the disabled states could create difficulties from a usability and accessibility perspective in terms of:
- Pale grey text is too low contrast for many people with visual difficulties
- Darker grey text (text of a higher contrast) would no longer convey the “greyed-out” disabled state convention
- Buttons/links that are visible but disabled create cognitive dissonance (you can see it, but you can’t use it)
- However, hiding button/links when they are disabled could leave confusing gaps in the layout (“is something broken? Should something be there? Did my tracker blocker block something again?”
![Screen_Shot_2018-04-23_at_14.46.22](/uploads/2e84660e465014e413d53a490963b0f3/Screen_Shot_2018-04-23_at_14.46.22.png)
![Screen_Shot_2018-04-23_at_14.46.31](/uploads/4dbd36f555e9f4dff9cc356b24964639/Screen_Shot_2018-04-23_at_14.46.31.png)
Some exploratory mockups/alternatives are required!
Some good related reading: [‘Disabled buttons suck’ on Axesslabs](https://axesslab.com/disabled-buttons-suck/)Laura KalbagLaura Kalbaghttps://source.small-tech.org/indienet/hallo-gent/-/issues/127Settings: Page flickers when header is updated2018-04-23T13:08:39ZLaura KalbagSettings: Page flickers when header is updatedAs the header is updated (by new character entry in text input, or profile image position moved) the whole page reloads/flickers.
Browser variations on macOS:
- Oddly, leaving **Safari** for another app and returning prevents it from ha...As the header is updated (by new character entry in text input, or profile image position moved) the whole page reloads/flickers.
Browser variations on macOS:
- Oddly, leaving **Safari** for another app and returning prevents it from happening (cache?)
- Flickering persists in **Firefox**
- Occasional flickering when typing in text inputs in **Opera**, but seemingly not for any other fields
- **Chrome** is much like Opera (no surprise there) but has the occasional flicker (noticeably slower than other browsers) when refreshing the headerhttps://source.small-tech.org/indienet/hallo-gent/-/issues/126Settings: Behaviour of keyboard navigation on colour swatches should match mo...2018-04-23T13:08:37ZAral BalkanSettings: Behaviour of keyboard navigation on colour swatches should match mouse behaviour for same actions## To reproduce
1. Hover over colour swatches on the Settings page.
2. Note the behaviour of the swatches
3. Note that you have to perform a second action (click) to select one in order to change the theme colour.
4. Navigate via keybo...## To reproduce
1. Hover over colour swatches on the Settings page.
2. Note the behaviour of the swatches
3. Note that you have to perform a second action (click) to select one in order to change the theme colour.
4. Navigate via keyboard to the colour swatches and navigate between swatches
## What should happen
Keyboard navigation should behave the same way as mouse navigation (navigating to a swatch should not select it. Selecting it – e.g., via Space – should select it.) This is also consistent with how buttons work in general.
## What does happen
Simply navigating the swatches via keyboard changes the theme colour.https://source.small-tech.org/indienet/hallo-gent/-/issues/125Fix validation syntax for secret code2018-04-23T08:39:25ZAral BalkanFix validation syntax for secret codeThe validation syntax for a correct code should be of the form:
`.*?-.*?-\d\d\d\d`
Currently, it is validating as correct at:
`.*?-.*?-\d`The validation syntax for a correct code should be of the form:
`.*?-.*?-\d\d\d\d`
Currently, it is validating as correct at:
`.*?-.*?-\d`https://source.small-tech.org/indienet/hallo-gent/-/issues/124Bug: Changing Name or Bio field in Settings screen makes the name/bio fade in...2018-04-20T14:04:20ZAral BalkanBug: Changing Name or Bio field in Settings screen makes the name/bio fade in/out on every letter## To reproduce
1. Transition to Settings screen
2. Change the name or bio
## What should happen
The corresponding text in the header should update without a transition
## What actually happens
The corresponding text in the header u...## To reproduce
1. Transition to Settings screen
2. Change the name or bio
## What should happen
The corresponding text in the header should update without a transition
## What actually happens
The corresponding text in the header updates with a dissolve transition
https://source.small-tech.org/indienet/hallo-gent/-/issues/123Hallo.gent profile image should fade in during the transition from the index ...2018-04-23T09:37:56ZAral BalkanHallo.gent profile image should fade in during the transition from the index page to the Settings page## What happens
�The Hallo.gent profile image is replaced with the generic profile image too early, which is confusing, as the other elements are not. (It is currently replaced when a valid code has been entered).
## What should happen...## What happens
�The Hallo.gent profile image is replaced with the generic profile image too early, which is confusing, as the other elements are not. (It is currently replaced when a valid code has been entered).
## What should happen
The Hallo.gent profile image should cross-dissolve into the generic profile image during the transition from the index page to the Settings page (after the person selects the Settings link in the nav.)https://source.small-tech.org/indienet/hallo-gent/-/issues/122Use gender neutral language in the readme2018-04-23T10:05:12ZAral BalkanUse gender neutral language in the readmeReplace “he” with “they”, etc.Replace “he” with “they”, etc.