webcomponents | A short introduction to Web Components | Learning library

So I have an application which uses vaadin (14) and the keycloak spring boot adapter (11). I looked at keycloaks authorization example for spring boot called "app-authz-springboot" available here: https://github.com/keycloak/keycloak-quickstarts/tree/latest/app-authz-springboot When i execute the example everything works fine but when i wire up my vaadin application to the keycloak instance from the example and copy the application.properties file from the spring half of the same example it fails to set up the policy enforcement configuration. it gives me the error message:

If I look at the polymer shop I am instantly sold on wanting to use this as a starter for my web shop. Not just because it's already a web shop (full pwa technology) but because it has excellent (offline) experience on browser/mobile, has proper documentation and is still maintained.

But then look at the polymer home page and see the project is based on an outdated polymer version and even the fact that it's using polymer in the first place is curious:

The Polymer library is in maintenance mode. For new development, we recommend Lit.

So my question is if lit will have the rich choice of web components that the shop seems to be depending on?

This may be a dumb question but I skipped polymer other than looking at some exciting news in google IO

I have a Vaadin 14.0.10 app with Spring Boot and a Spring Security configuration. I'm trying to update it to 14.5.4, but after the update, I get a blank page when I try to load the app. There are no errors on the server logs, but on the browser console, it shows two errors:

I'm using Azure to host my Java Spring Boot application. I have created a trial to test this solution and I managed to deploy my application following this tutorial Deploy with Azure which is using the azure-webapp-maven-plugin and the command mvn azure-webapp:deploy.

My problem is that when I'm making changes inside my application and I want to apply them in my Azure Web App but nothing actually update when I reach the page, here is the message after using the deploy command :

WebComponents property setter not trigger if property defined before. As follows:

I have a project built on MAC and the package.json script is as follows:

I have seen almost all the similar posts, but I am unable to resolve it using those steps. I have been trying to create a web component using Angular 9. Angular version and details are :

I am trying to get a webcomponent working with vitejs.

component I am trying to use: https://www.webcomponents.org/element/input-knob

I did as describe in the docs.

install and setup @vitejs/plugin-vue

https://github.com/vitejs/vite/tree/main/packages/plugin-vue#vitejsplugin-vue-

initiate the customelement in config. ( I also tried simply putting the custom element in main.js https://github.com/vitejs/vite/issues/1312

vite.config.js

Problem summary I am using webcomponents in elm 0.19.1. Goal is for the webcomponent to emit an event if the webcomponent attribute "requeststate" changes. The event is emitted (I can see in the the logging in the webcomponent constructor), but elm is not firing the 'WebcomponentEvent' correctly. Problem is on both windows 10 and ubuntu 16.04, firefox and chrome. Didnot test older elm versions.

Steps to reproduce:

• I have the problem reproduced in this minimal repo: https://github.com/Derryrover/elm_webcom_bug
• Compile elm with: elm make src/Main.elm --output elm.js --debug
• use a webserver (for example 'serve') to host locally
• click the button 'request'. This will change the attribute 'requeststate' on the webcomponent. That in turn triggers the custom event 'created' on the webcomponent. But elm does not receive this event..

Opening the elm-debugger or clicking the 'request' button again will magically make the event fire in elm. Strange. Also I have made the branch 'tom-experiment'. In this branch I got the event from webcomponent-click working, but only if I directly click on the webcomponent itself.

The importance of this problem Why do I want to trigger an event on a webcomponent by changing an attribute? Goal of this approach is also JavaScript interop. For example I can now use this webcomponent to create a date-time or uuid or do some other javascript magic. This way I can work around ports completely. A solution for this problem might settle the entire Javascript interop discussion !

Code

This is my Main.elm: