'sizes' in TileGrid is ignored

Hello,

and thanks for your time and effort to understand my problem description. 😃

Greetings.

Describe the bug Maybe i’m too dumb to understand it, but when i set the ‘sizes’ property of the TileGrid, the Tile Image Source is still making requests to tiles outside of min/max x/y.

This is my grid as TileDebug shows it. I restrict it with an extent, for sure, but also with “sizes” as you can see below the image:

The TileGrid is successfully creating the “fullTileRanges_”

fullTileRanges_: Array(4)
0: t {minX: 0, maxX: 0, minY: 0, maxY: 1}
1: t {minX: 0, maxX: 1, minY: 0, maxY: 3}
2: t {minX: 0, maxX: 1, minY: 0, maxY: 3}
3: t {minX: 0, maxX: 10, minY: 0, maxY: 15}

1: t {minX: 0, maxX: 1, minY: 0, maxY: 3}

Until this point everything seems fine, but “fullTileRanges_” is ignored by the Layer/Source and creates requests for the following coords (z, x, y):

OutOfRange [1, 2, 0]
OutOfRange [1, 2, 1]
OutOfRange [1, 2, 2]
OutOfRange [1, 2, 3]

(I catch those requests in my “tileLoadFunction” (and tileloadstart event))

Hm … maybe its a hint that its only exceeding the X bounds … ?

To Reproduce Define your own TileGrid (restricted by “sizes” property) for your TileImage for your layer.Tile …

Expected behavior TileImage should not query tiles which are outside of the bounds of sizes/fullTileRanges_.

[ahocevar]

#11532 now fixes this issue - not by changing the documentation, but by implementing what the documentation says.

[ahocevar]

Fixed with #11532