demike

I think the best would be to remove all styles and properties (including their entries in __get, __set). But add two setter/getter methods (rename get|setCustomAttribute|Style) setAttribute($strAttr,$mixVal), setStyle($strStyleAttr,$mixVal), get ... ,...

> : {array: [], statusCode: StatusCode } { => > I beleve that array could be a [] or a Buffer > > so return value should be > :...

What would be the benefit of forbidding custom decorators? Could you elaborate. I mean this draft makes me nervous because our application(s) heavily rely on custom decorators. We use decorators...

Can you provide a minimal example that reproduces the problem?

If you think about making template and templateUrl 'inheritable'. You should also consider styles and styleUrls. Because you also do not have access to the upstream css/scss files

According to a three.js comment (https://discourse.threejs.org/t/load-texture-to-obj/32451/2) you could inject a `TextureLoader` and `ObjLoader` in your class and then recursively apply the texture. Simplified Example: ExampleComponent.ts ```ts // ... public async...

The modified on-demand-rendering example works as expected ``` Render On-Demand orbit map arcball transform drag fly trackball firstpersion Change Mode ``` ``` import { ChangeDetectionStrategy, Component } from '@angular/core'; import...

You are right. PixelRatio is missing. There is a setter on the Renderer and this one is not called. I will add the possibility to set it by means of...

I will implement automatic device pixelratio setting. This will be done before rendering a frame, if the device pixel ratio changed ( imagine moving the window from one screen to...

automatic pixel ratio adjustment is implemented in v0.16.0.