Please! Stop with the mobile web sites! If you are using browser agent strings to change your CSS/layout don't! Use responsive CSS instead. There are other situations when you need a small window and devices that have a small screen where your web site does not work.
-
-
Minimal Accessible Tooltip
Doing a lot of accessibility (a11y) fixes, I wondered what would be the minimum amount of code to create a WCAG 2.1 compliant custom tooltip. Unfortunately, it had to include Javascript. Here is what I can up with.
-
Day-to-day with Librem 5
After quite a few years of waiting, I finally got my Librem 5 phone. I am now using it as my primary phone… using my work phone as a back-up. Here are the issues and whether I think using it as a primary phone is a good idea so far.
-
If you are wanting to apply accessibility labels onto an image, here are the label (
alt
,title
,aria-description
,aria-label
) priorities (highest first):aria-description
(witharia-label
,alt
ortitle
);aria-label
;alt
. Notearia description
does not get read out if there is no other label attributes. (Tested on Windows, NVDA, and Firefox and Edge). -
Email dates in Javascript
Javscript is missing functions to format dates in some common formats, such datetime-local inputs and RFC 5322 (email dates) in a non-obsolete way. While Date.toUTCString() is close, the timezone is now obsolete (though it is handy for HTTP Date and other such headers). Here's the basic functions to get the right formats
-
Visibility and CSS Accordians
When changing a reworked menu to have accordian animations, I came to the realisation that I have been missing a big issue when using
max-height
transition
animations — accessibility. I detail a simple fix in this article. -
Can't touch list
Turns out screen readers really don't like you playing with the
display
CSS property on lists, for example to change it to an inline list — it will cause lists items to be read like a paragraph. Here's how to do without upsetting the screen readers. -
New Zealand Low Power Networks (LTE-M & NB-IoT)
I have started experimenting with low power wide area networks (LP-WAN) in New Zealand using a u-blox SARA-R410-02B. Here is what I have experimented with so far.
-
JS Binary Decoder
I have recently been dealing with parsing binary data packets from various sources, and have published two NPM libraries from it: binary-decoder and sbd-direct-ip. Here's how they came to be.
-
Starting with ESP32
I started developing my trap-watch project on an ESP32-CAM using the ESP IDF. Here is the newbie difficulties I ran into.
-
VIM Window Rabbit Hole
Developing ESP-IDF components I thought it would be great if I could make a command to open all the files for a component at once. What a rabbit hole it was. Here is how I did it.
-
Parsing Arguments in Bash
Making a script parse arugments in Bash took me way too long last time I did it, so here is a nice full example of how to do it using
getopt
-
Where's my bait gone?
I have recently started trapping some introduced predators around my local area and have had baits and pre-feed disappear with nothing to show for it, so I decided to get sparky and see if I could catch the culprit in the act.
-
Bathymetric Contours
Finally got around to creating a SLD style for GeoServer to display bathymetric contour lines using the GEBCO gridded bathymetric data. Here's how.
-
shm That Cache
I am often trying to find more space on my hard drives and found today my own docker containers wasting space thanks to ! Here's how I fixed it.
-
Blob blob blob blob Stayin' Alive Stayin' Alive
Upon recently trying Deezer again, I found their web app ate all my memory when running in Firefox, so I decided to see if I could find out why. I got as far as memory-file-data/string and Blobs. Here's how.
-
A new Litter Survey
In a culmination of litter surveys and litter picks, linked data and data exploration, and remoteStorage and ActivityPub, I have created a web-based litter pick/survey app that I hope will allow federated citizen science.
-
Hoe Stream Trash
My latest litter pick target was Hoe Stream and the White Rose Lane Local Nature Reserve. Here's how it went.
-
Release the Beast
I just created a Gitlab CI job to create a release with information from a CHANGELOG.md file for some of my projects. Here's how I did it.
-
Gitlab CI Caching
I noticed something strange happening during build process during a multi-tasking bug fix. Turns out I was using Gitlab CI's caching incorrectly. I should have been using artifacts. Here's what I saw.
-
Birthday Trash
As a birthday treat, I took the day off work to try out my electronerised litter picker. Here's how it went.
-
Pi Trash Cam
In preparation for a day of litter picking, I finally got round to a project idea - attaching a camera to a litter picker to record it all. Here's what I did.
-
yarn add --dev webdriverio
I finally started implementing UI testing on first-draft using WebdriverIO. While writing tests was easy, getting the tests running was a little more difficult. Here is how I did it.
-
Hooray! My new blog is live! Based on Sapper, using MongoDB and eventually ActivityPub and ActivityStreams, it will be my federated posting hub to the world.
-
Removing EXIF Data from Photos
Creating this new blog, I wanted to make sure there was no metadata data leaking personal information. Here's how I removed all the metadata tags except the ones I wanted from my photos.
-
tmux List and Reattach
Using
tmux
for your terminal multiplexer but want an easy to reattach to a session? Here's a small bash script to do it. -
Selectable Shell Examples
Here's how to help your readers save time by making your post's shell commands easy to select and copy - with a simple CSS property.
-
Be Dates You
Making my new blog, I didn't initially set the published dates to be native dates in the database. Here what I did to change them …and do all the upgrades I needed.
-
Testing vue components
I recently needed to test that some Vue components were creating the correct HTML. To do this, I decided to create snapshots of Object representations of the rendered HTML.
We recently started on building our own json-schema form generator for use in our application. We decided to go down the route of creating our own instead of using one of the various ones already available as we needed our forms to have some custom functionality, including validation warnings and extended descriptions.
One of the things that fell on me to complete was getting the basic functionality around
array
types working. After reorganising the code logic to be able to work with arrays and getting the basic generation functionality working along with a storybook showing off the functionality, I decided it was about time to write some tests for the components I had created.Writing Tests
Writing tests for the mixins and the utility functions was nice and simple, but writing tests to ensure that a component is spitting out what it should has always haunted me. Using jest and vue-test-utils I was able to create a wrapped shallow instance of the component under test. I then looked into ways to testing if it was what I expected, but there wasn't any great methods that I could see. Using the
wrapper.html()
function returned very unhelpful results (example below) that hid all the information I was wanting to check, like the values of the passed props. Digging into thevm
or thevnode
of the instance was just going to be too painful on some of the more complex components. So I decided to create my own utility function.Output of
wrapper.html()
function<container-stub formid="form-generator-2/" schema="[object Object]" config="[object Object]" fieldconfigs="[object Object]" value="hello" required="true" path=""></container-stub>
instanceComponentObject()
The functionality I wanted was something I have used in previous tests. In those, I called render functions with a custom
createElement/h
function that simply returned an Object with the tag of the component, the props passed to the component, and the children given to the component.result = { tag: 'container-stub', props: { formId: 'form-generator-2', schema: { type: 'string', title: 'A String' } config: {} fieldConfigs: {} value: 'hello', required: true, path: [] }, children: [] }
To do this. I ended up recursively going through the instance's
vnode
s andchildren
and returning Objects to represent them. I initially did it using thevm
, but found that it squashed a lot of the elements down into single children and the results were again not very handy./** * Convert an vnode into a Object representation of it with its tag, * props and children * * @prop vnode VNode to convert to an Object representation * * @returns An Object representation with tag, props and children values */ export const componentObject = (vnode) => { return ( vnode.text || { tag: vnode.componentOptions?.tag || vnode.tag, props: vnode.data?.props, children: (vnode.children && vnode.children.map((child) => componentObject(child))) || [] } ); }; /** * Convert the wrapper instance into to an Object representation of * the vnode including tag, props and children * * @prop instance Instance to convert * * @returns An Object representation of the vnode */ export const instanceComponentObject = (instance) => { return instance.vnode && componentObject(instance.vnode); };
(for those who haven't seen the interesting sytax before, the
?.
is the new optional chaining)Capturing Snapshots
Once I had the helper function in hand, I was able to easily create an instance of a component (using another helper function to create a shallow mounted instance) and compare the output of my function against the Jest snapshot
import { shallowMount, createLocalVue } from '@vue/test-utils'; import Vuetify from 'vuetify'; import Vue from 'vue'; import FormGenerator from '~/src/form/components/FormGenerator'; import { instanceComponentObject, createInstance } from '~/tests/helpers/vue'; Vue.use(Vuetify); /** * Shallow mount a component to create an instance of the component * * @prop component Component to create a shallow instance of * @prop props Props to pass to the component * @prop options Options to pass to shallowMount */ const createInstance = (component, props, options) => { const localVue = createLocalVue(); const vuetify = new Vuetify(); return shallowMount(component, { localVue, vuetify, propsData: props || {}, ...options }); }; test('it gives config, fieldConfigs, formId and require to Container', () => { const fieldConfigs = { field: {}, 'sub/field/deep': {} }; const wrapper = createInstance(FormGenerator, { schema: { type: 'object', properties: { field: {}, sub: { type: 'object', properties: { field: {} } } } }, config: { fields: fieldConfigs } }); expect(instanceComponentObject(wrapper)).toMatchSnapshot(); });
Pesky Asynchronous Components
All was well after creating tests for two of the components and reviewing the created snapshots carefully to ensure they were correct. However, the third component, the container for array types, returned some strange results - everything was there except for the actual fields.
The snapshot from before the fix without the fields
exports[`render simple array with a current value 1`] = ` Object { "children": Array [ ..., Object { "children": Array [ Object { "children": Array [ Object { "children": Array [], "props": Object { "icon": true, }, "tag": "v-btn", }, ], "props": undefined, "tag": "v-col-stub", }, ], "props": undefined, "tag": "div", }, Object { "children": Array [ Object { "children": Array [ Object { "children": Array [], "props": Object { "icon": true, }, "tag": "v-btn", }, ], "props": undefined, "tag": "v-col-stub", }, ], "props": undefined, "tag": "div", }, ..., ], "props": undefined, "tag": "div", } `;
After a little digging, I realised that this was because the component dynamically imports a higher level container component. This is because it is the same container component that creates the array container component, so it is set as
undefined
in the array container. To get around this, I was able to force vue-test-utils to stub the component so that it produced the output as expected.The test with the forced stub.
test('with a current value', () => { const wrapper = createInstance( ArrayContainer, { schema: { type: 'array', title: 'Title', description: 'Some description', items: { type: 'string', title: 'String' } }, formId: 'test', value: ['one', 'two'] }, { stubs: { Container: true } } ); expect(instanceComponentObject(wrapper)).toMatchSnapshot(); });
The snapshot with the stub forced, now happily with the fields/container component showing.
exports[`render simple array with a current value 1`] = ` Object { "children": Array [ ..., Object { "children": Array [ Object { "children": Array [], "props": Object { "config": Object {}, "fieldConfig": undefined, "fieldConfigs": undefined, "formId": "test", "path": Array [ 0, ], "required": true, "schema": Object { "title": "String", "type": "string", }, "value": "one", }, "tag": "container", }, Object { "children": Array [ Object { "children": Array [], "props": Object { "icon": true, }, "tag": "v-btn", }, ], "props": undefined, "tag": "v-col-stub", }, ], "props": undefined, "tag": "div", }, Object { "children": Array [ Object { "children": Array [], "props": Object { "config": Object {}, "fieldConfig": undefined, "fieldConfigs": undefined, "formId": "test", "path": Array [ 1, ], "required": true, "schema": Object { "title": "String", "type": "string", }, "value": "two", }, "tag": "container", }, Object { "children": Array [ Object { "children": Array [], "props": Object { "icon": true, }, "tag": "v-btn", }, ], "props": undefined, "tag": "v-col-stub", }, ], "props": undefined, "tag": "div", }, ..., ], "props": undefined, "tag": "div", } `;
Hooray.
-
No More Numbers
HTML5 number inputs aren't useful, but tel inputs, have all the power
-
A Hacker "Hacked" Me
I decided to look into the extortion emails I have been getting and wrote a small script to extract the bitcoin addresses that have been used.
-
Mouse Surgery
As part of my pledge not to upgrade, I decided to repair two of my failing mice instead of replacing them with a brand new model (as tempting as it was). Here's what I did.
-
Danger Danger, Highly Reactive
-
Switching to SSR
-
Clean Docker Registry
-
Testing on the Filesystem
-
NaN Got Me
-
All our app's tabs are belong to us
-
Developing NPM modules
-
Nfa + Nfb or N(f+fa+fb)
-
Photo Layout
-
Browning Pass HideAway Web Site
-
Think Mobile
-
Pledge to Refuse and Not Buy Bottled Water
-
Run PHP run!
-
Gallery Hierarchy
-
I'm making hierarchies
-
Google Sheets fun
-
Travel Photos
-
Image managment scripts
-
MeldCE logo
-
MoltenDB
-
The Expensive Side
-
abcde
-
Energizer Power Plus Rechargeable Batteries
-
USAR FOGTeX
-
Personal Gear Bag
-
Geocaching Stamp
-
Call Record Presenter
-
Kimi Ora School
-
All About Catering Web Site
-
Quantum Accounting Web Site