Hi
Kauybv8
Kfibbudvbib

ViewRotateIconsOnRoadsBug.zip
When rotating the map, the icons on roads like directions and oneway arrows stay the same direction canvas wise. They should rotate with the road of course.

This is a little bit unrelated to this repo, but I noticed a neat UI framework being used on https://xyz.api.here.com/token-ui/, called "LUI", and I see custom elements in the page named with the prefix lui-.

The UI looks very nice!

I was wondering if this UI kit is available anywhere? If not, are there any plans to open-source it?

As an experiment, I was able to place the script https://xyz.api.here.com/token-ui/js/lui-all.min.js onto my own page, and play with some components, but this comes with no documentation (and may be of questionable legality).

The LUI framework looks very interesting. It'd be neat to use it!

If one sets the font property as a function for a style type "Text", it will not be interpreted correctly in the webgl renderer (or apparently not called at all). In the canvas renderer it is.

To reproduce, find the playground sample attached:
font as function does not work.html.zip

I'm trying to overlay an xyz-maps Map instance over a vector map rendered using MapLibre (but this is also reproducible when trying to get the background color / image of the Map's container to bleed through).

Prior to 071ff56, I was able to make the background transparent while keeping features rendered at full opacity using the following diff (quick and dirty; there were surely side-effects I wasn't seeing):

diff --git i/packages/display/src/displays/BasicDisplay.ts w/packages/display/src/displays/BasicDisplay.ts
index 2b4f6ef..7aa15ca 100644
--- i/packages/display/src/displays/BasicDisplay.ts
+++ w/packages/display/src/displays/BasicDisplay.ts
@@ -572,13 +572,19 @@ abstract class Display {
             bgColor == 'rgba(0, 0, 0, 0)' || // webkit
             bgColor == 'transparent' // firefox, ie
         ) {
             bgColor = '#ffffff';
         }
 
+        bgColor = color || 'rgba(0, 0, 0, 0)';
+
         bgColor = render.convertColor(bgColor);
 
         displ.globalBgc = bgColor;
 
         render.setBackgroundColor(bgColor);
     }
 
diff --git i/packages/display/src/displays/webgl/GLRender.ts w/packages/display/src/displays/webgl/GLRender.ts
index d5d4b74..d5edb91 100644
--- i/packages/display/src/displays/webgl/GLRender.ts
+++ w/packages/display/src/displays/webgl/GLRender.ts
@@ -196,7 +196,7 @@ export class GLRender implements BasicRender {
     setBackgroundColor(color: RGBA) {
         // this.clearColor = color;
         if (this.gl) {
-            this.gl.clearColor(color[0], color[1], color[2], 1.0);
+            this.gl.clearColor(color[0], color[1], color[2], color[3]);
         }
     }
 
diff --git i/packages/display/src/displays/webgl/program/Program.ts w/packages/display/src/displays/webgl/program/Program.ts
index d31e1a7..bcd3845 100644
--- i/packages/display/src/displays/webgl/program/Program.ts
+++ w/packages/display/src/displays/webgl/program/Program.ts
@@ -35,7 +35,7 @@ type AttributeMap = { [name: string]: Attribute | ConstantAttribute };
 type ColorMask = { r: boolean; g: boolean; b: boolean; a: boolean };
 
 const DEFAULT_COLOR_MASK: ColorMask = {
-    r: true, g: true, b: true, a: false
+    r: true, g: true, b: true, a: true
 };
 
 const NO_COLOR_MASK: ColorMask = {

With bd1d34e (HEAD), I can make the background almost transparent (this.gl.clearColor(color[0], color[1], color[2], color[3] || 1.0) means providing a color with an alpha component of 0.0 results in a value of 1.0), but it applies the background's transparency value to everything that's rendered (presumably because of a color mask that's different from 071ff56).

createFeatureContainer fails when features are passed to the builder:

const feature = editor.getFeature("<id>", layer);
editor.createFeatureContainer([feature]);
xyz-maps-editor.min.js:19 Uncaught TypeError: e.getProvider is not a function
    at e.add (xyz-maps-editor.min.js:19:114888)
    at e.push (xyz-maps-editor.min.js:19:92660)
    at e.createFeatureContainer (xyz-maps-editor.min.js:21:10611)
    at index.js:178:30
    at t.trigger (xyz-maps-common.min.js:5:5183)
    at x (xyz-maps-display.min.js:5:186164)
    at Tn.onPointerUp (xyz-maps-display.min.js:5:187068)

This works fine:

const feature = editor.getFeature("<id>", layer);
const container = editor.createFeatureContainer();
container.push(feature);

Defining "side" of a zone as "L" or "R", should render the zone to indicate, that it applies to the defined side.

This is not working anymore. The zone is always rendered as if it applies to both sides.

Can be reproduced in this playground example:
https://xyz.api.here.com/maps/latest/playground/index.html#editor_Zone%20Selector

If a display backgroundcolor is set, the layer backgroundcolor is ignored. Expected is that always the layer background color is used if set.

XYZ Maps docs still refers to using XYZ Token In Readme.md and Docs pages which is currently failing with 404,

Setup your XYZ token
Setup an XYZ token is only required if the XYZ Hub endpoint at xyz.api.here.com is used. You can get a token by following the instructions in this guide.

If you are using a local XYZ Hub simply set set-access-token to an empty string.

Running integration tests / playground and debug pages requires the XYZ token to be provided.

Configure your XYZ token
yarn run set-access-token YOUR_ACCESS_TOKEN

Can reproduced with this adjusted playground sample:
Add empty array to layer.html.zip

In the case of MultiPolygon, some of the outlines of Polygon does not render as expected.
XYZChairsRendering.zip

FireFox, Windows 10. Zooming with mouse wheel is very slow.

Setting display behaviour to "fixed" workarounds the problem as one mouse wheel click is one zoom level in every browser.