Hi Hristo,

From the last PNG it looks like the function call you are in has been invoked on the proxy and not the actual type, so the field that is passed in as the first parameter is undefined. I might be able to tell you more if I see the call stack. In particular, we want to find the first stack frame where a method on HeaderMenu is invoked. Is there a package private method you are using on this type? The container cannot proxy package private methods, so if you call a package private method from the outside of an @ApplicationScoped beans it will not be redirected to the actual instance and could cause a problem like this.

Without knowing the reason for the resriction, I think there should be a better way to handle this - a runtime warning at a minimum. Mystery JS errors is not OK.

There are warnings about this in the build logs, but we can't fail the build for this because it would make it impossible to have @ApplicationScoped classes extending Widget.

I also noticed that for Element injection you have to provide @Named("tag"). I saw that in the console log at runtime.

I'm not sure what logging you're referring to. You don't always have to use the @Named to inject an element. That's only necessary if there is ambiguity (i.e. for elements that have multiple tags). As per the CDI spec @Named beans are also @Default, so if there is only one bean satisfying an element (like the @Named("a") Anchor) you do not need the @Named on the injection site. In cases where the @Named is necessary you should see rebind errors for ambiguous dependencies.