xstable Github contribution chart
xstable Github Stats
xstable Most Used Languages

Activity

22 Sep 2022

Xstable

started

Started On 22 Sep 2022 at 08:24:50
Issue Comment

Xstable

Add a few provider by default
Forked On 21 Sep 2022 at 07:56:02

Xstable

@mariusandra can this issue be closed? Seems to be solved by you?!

Commented On 21 Sep 2022 at 07:56:02
Issue Comment

Xstable

Make Warning-Overlays more configurable

A way to configure the animation-type and delay for the metaWheelZoomWarning and twoFingerDragWarning would be awesome.

At least needed:

  1. transition type to show/hide overlay
  2. delay for animation of showing/hiding
  3. opacity & color of the Overlay

You added a functionality, that after a given amount of time, where no page-scroll appear and the pointer is above the map... if you scroll then again, the Warning-Layer appears. That's an awesome feature. But would be nicer if we could adjust this time for own needs... or to be able to acivate that feature after user clicked at least once at the map.

Forked On 21 Sep 2022 at 07:55:13

Xstable

@mariusandra add this as hacktoberfest2022 issue and assign it to me, and I'll solve this.

Commented On 21 Sep 2022 at 07:55:13
Started

Xstable

started

Started On 09 Sep 2022 at 01:19:08

Xstable

defineStringField (Zeichenkettenfeld #1) don't work

in the Browser-Plugin I have defined an additional String-Field:

image

Now in the Browser, I'd like to assign the value of this "Additional Property" to an input-field in a page:

image

If I click on the blue button, it assign "Zeichenkettenfeld #1" to it: image

But even If I reload the page and try to let keepassxc-plugin fill the input-fields, there are never any value in this assigned field.

Question

Am I doing something wrong? Is there (and if, how) a way to assign the previous created {S:ZUGANGSNR} to an Input-Field?

Debug info

KeePassXC - 2.7.1 KeePassXC-Browser - 1.8.1 Operating system: Linux x86_64 Browser: Chrome/Chromium 104.0.5112.81

Forked On 20 Aug 2022 at 11:14:37

Xstable

Today it works without changes. It might be that I need to fully reboot the browser and keepass to make it work

Commented On 20 Aug 2022 at 11:14:37

Xstable

defineStringField (Zeichenkettenfeld #1) don't work

in the Browser-Plugin I have defined an additional String-Field:

image

Now in the Browser, I'd like to assign the value of this "Additional Property" to an input-field in a page:

image

If I click on the blue button, it assign "Zeichenkettenfeld #1" to it: image

But even If I reload the page and try to let keepassxc-plugin fill the input-fields, there are never any value in this assigned field.

Question

Am I doing something wrong? Is there (and if, how) a way to assign the previous created {S:ZUGANGSNR} to an Input-Field?

Debug info

KeePassXC - 2.7.1 KeePassXC-Browser - 1.8.1 Operating system: Linux x86_64 Browser: Chrome/Chromium 104.0.5112.81

Forked On 19 Aug 2022 at 04:34:58

Xstable

I did, the screenshot only shows the selection of the first one. I've added username and password after that. Anyway, first field are never filled with data.

Commented On 19 Aug 2022 at 04:34:58

Xstable

defineStringField (Zeichenkettenfeld #1) don't work

in the Browser-Plugin I have defined an additional String-Field:

image

Now in the Browser, I'd like to assign the value of this "Additional Property" to an input-field in a page:

image

If I click on the blue button, it assign "Zeichenkettenfeld #1" to it: image

But even If I reload the page and try to let keepassxc-plugin fill the input-fields, there are never any value in this assigned field.

Question

Am I doing something wrong? Is there (and if, how) a way to assign the previous created {S:ZUGANGSNR} to an Input-Field?

Debug info

KeePassXC - 2.7.1 KeePassXC-Browser - 1.8.1 Operating system: Linux x86_64 Browser: Chrome/Chromium 104.0.5112.81

Forked On 19 Aug 2022 at 02:47:30

Xstable

thanks a lot @varjolintu for your answer.

I've tried this, didn't get it to work.

image

And in the Plugin in the browser I still only see this Zeichenkettenfeld #1 which are not replaced. Any Idea, what the issue might be.

Commented On 19 Aug 2022 at 02:47:30

Xstable

started

Started On 13 Aug 2022 at 10:33:52

Xstable

Update README.md

Created On 02 Aug 2022 at 03:36:55

Xstable

Update README.md

This fix #1

Pushed On 02 Aug 2022 at 03:36:46

Xstable

A TypeScript client for the Toogl Track API (v9)

Forked On 02 Aug 2022 at 03:35:54
Issue Comment

Xstable

TypeError: Toggl is not a constructor

Hi, I have the following code

import Toggl from 'toggl-track';

const toggl = new Toggl({
    auth: {
        token: '',
    },
}); 

and I'm getting this error

const toggl = new Toggl({
              ^

TypeError: Toggl is not a constructor 

where might be the issue?

Node version: v16.14.0

"toggl-track": "^0.7.1"

Thanks in advance!

Forked On 02 Aug 2022 at 03:35:30

Xstable

There are two issues in the example-code. Use those for testing:

import {Toggl} from 'toggl-track';

const toggl = new Toggl({
  auth: {
    token: process.env.TOGGL_TRACK_API_TOKEN || "48993d0cf18bb9ef6bd9f1ac53742a18",
  },
});

const entries = await toggl.timeEntry.list();
console.log(entries); 

Commented On 02 Aug 2022 at 03:35:30

Xstable

Toggl API for Node.js

Forked On 02 Aug 2022 at 02:07:24
Issue Comment

Xstable

URL matching don't work on Android 12

I've switched ny device and from Android 9 to Android 12. On both devices, I do use brave browser (fork of chromium) At android 9 it work as expected, if I open the keepass-keyboard from a web formular... Means, keepass search for the url to find the credentials.

But on android 12, the reference is always the package name of the app: com.brave.browsee

Screenshot_2022-07-27-19-41-02-916_keepass2android keepass2android

How can I fix this?

Forked On 29 Jul 2022 at 11:33:51

Xstable

I'd also give KeePassDX a try, with same result. As caused of this, I think it's an issue upcoming with Android 12?!

Commented On 29 Jul 2022 at 11:33:51
Issue Comment

Xstable

Error on fingerprint init (quick unlock)

I have the following error on Poco F3 / Android 12, if I try to use fingerprint to unlock:

IMG_20220719_202615_671

Before at my xiaomi a1, Android 9, it works like expected.

Forked On 29 Jul 2022 at 11:29:47

Xstable

The fingerprints are brand new, as this is a new device. I've tried to deactivate and reactivate (even with fully closing the app in between), but same result.

Commented On 29 Jul 2022 at 11:29:47