#12743 Add support for Fragment response in GetFeatureInfo

[Binabh]

Description

Fixes for case when GetFeatureInfo sends fragment response

Please check if the PR fulfills these requirements

• The commit message follows our guidelines: https://github.com/geosolutions-it/MapStore2/blob/master/CONTRIBUTING.md
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (check one with "x", remove the others)

• Bugfix

Issue

What is the current behavior?
#12743

What is the new behavior?
Fragment response from GetFeatureInfo are properly shown

Breaking change

Does this PR introduce a breaking change? (check one with "x", remove the other)

• Yes, and I documented them in migration notes
• No

[stefanocudini]

dear @Binabh

I checked the code and the unitetests are fine when displaying the identify content in HTML.

But there's a strange precision issue with the click identify.
It's very difficult to center any value for the lizmap layer (mentioned in the linked issue #12743).
At a quick glance, there doesn't appear to be anything in this PR that could cause this bug, but it's replicable in this branch.
Below are the identify attempts; some work, but they're few.

Peek.2026-08-06.15-49.mp4

[Binabh]

@stefanocudini Thank you for your review. Yes this is pretty annoying and I also faced this.

This seems to be issue with Lizmap threshold set using Lizmap QGIS plugin as seen here on page 57.

I also tried to host lizmap project locally as that would give us control over tolerance value but it was very difficult to get the setup right for me.
Looks like for this demo server threshold is set to 0 or very low value.

[stefanocudini]

@stefanocudiniGrazie per la tua recensione. Sì, è davvero fastidioso e anche io ho riscontrato lo stesso problema.

Sembra che il problema riguardi la soglia di Lizmap impostata tramite il plugin Lizmap per QGIS, come si può vedere a pagina 57.

Ho anche provato a ospitare il progetto lizmap in locale, dato che ciò ci avrebbe permesso di controllare il valore di tolleranza, ma è stato molto difficile configurarlo correttamente. Sembra che per questo server demo la soglia sia impostata a 0 o a un valore molto basso.

mmmh I understood, I actually tried to check the request and the bbox is quite large.
request=GetFeatureInfo&BBOX=-8185522.098096532,4993112.772247052,-8184557.080614566,4994077.789729018
about: 1km

I just saw the next PR: #12736
So this one can't solve this either. Is the problem confined to the specific Lizmap server-side right?

[Binabh]

@stefanocudini Yes, My understanding here is that it is related to Lizmap config rather than Mapstore2.
#12736 This solves different case when two layers are present.

[stefanocudini]

@stefanocudini Yes, My understanding here is that it is related to Lizmap config rather than Mapstore2. #12736 This solves different case when two layers are present.

ok, please @Binabh check the align with master there seem to be some conflicts