theme-default | Element default theme | User Interface library

It seems karma-jasmine-html-reporter@1.5.4 requires jasmine-core@">=3.5" but you have jasmine-core@3.4.x.

In package.json, change jasmine-core to 3.5.0 or greater and run an npm install again. Maybe you should also try deleting node_modules and doing a fresh install.

With the help of a colleague in Reddit, I figured out that this is a problem with server-side rendering. To cope with it, I have followed the vue-notification documentation resulting in this enhanceApp.js file

This is what role="alert" is for.

It will interrupt a screen reader (as it is the equivalent of aria-live="assertive") with any immediately important information.

As this is a dialog you may instead want to look at role="alertdialog" to replace your role="dialog".

Additionally when you focus the alert don't make the "Login Failed!" text tabindex="0".

Instead use tabindex="-1" so that you can still focus it programatically but it does not end up in the focus order of the page.

The pattern you currently use will be tricky (not impossible) to get right as your "OK" (submit) button is within a form, so this will send screen readers into "forms mode", which behaves differently from normal reading mode.

As such if you are able to create a custom component there is a great writeup from deque on how best to implement an alertdialog

An example of the markup used there is as follows, notice the use of aria-describedby and aria-labelledby to maximise the chances of the alert being read correctly:

This may help but I've had issues with webdriver not clicking on a button when I use the id to find it. The work around I've found is using the xpath instead of the id. Like this, it's worth a try.

In you array tableData, each object has a value who is a string. So your sort method in comparing strings. But here I think you want to sort them by number.

What you need to do is update your method like that :

I believe this is working as designed. You will only see the /foo/ sidebar when the route starts with /foo/. So, you won't see the /bar/ sidebar until you go to a route/page that starts with /bar/. You may want to use Sidebar Groups if you want to group links together in a single sidebar that is displayed for every route.

The solution is quite silly... I just needed to transform the options read-only collection into a read-write collection (thus, removing the get).

Your selector is wrong:

I see several problems in your mixin.

Be sure that you are saving theme-color else you will get an error if is not in the local storage.