Patrick Lohan

Might it have something to do with lsp-mode expecting a language server called 'vls' to be actually the Vue language server and getting confused?

Bug still present. We have tried adding duration="0" (bound and unbound) to the transition elements (plus the class that gets stuff done), adding fake classes to the or the element...

We seemed to have solved it but was waiting to see if it turned up again whilst refactoring. It did, on Friday (thank god for 'no deploy Fridays' xD So,...

How is this progressing. Asking because we have a information rich and UI heavy app that is borked if the user selects a device accessibility font zoom on both Android...

It doesn't look like there's a way to stop the iOS/Android accessibility settings when opening our app. Am I missing something obvious? Our app has already been designed and written...

We use Nativescript-Vue and create a custom boolean prop (default true) that can be used in any text elements (labels/buttons etc.) that need to not have a11y settings.

May I give this a go @Splode ? I'd be using {N}ativescript-vue. I guess I'd create a feature branch?

New project using expo-cli but I see this is happening when people are using official cli too. Same usage of outdated packages that have vulnerabilities, even after 10 or so...

Same here. Tried reaching out on Slack. Doesn't look good to the manager when they already have doubts as to using something other than React!

7 days, any move on this? I could try to make a pull request? Referenced: https://stackoverflow.com/questions/59389440/nativescript-dev-webpack-moderate-vulnerabilities