-
-
Notifications
You must be signed in to change notification settings - Fork 144
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Question]: Target "_blank" disapeared on hyperlinks in popups #4728
Comments
Quick guess, the popup content is "sanitized" to increase security
|
I would propose indeed to add target in the allowed attributes. We could implement a specific web component to replace these anchor with target blank in the future. |
Nice idea as well, a good proposal, with a Javascript magnifier, like on X when clicking on a picture to check if Lizmap is used on these big screens :) https://twitter.com/PompiersHerault/status/1826339477163503735 :) |
Thanks for your feedback ! Yes it would be nice to be able to keep the use of |
Thanks for reporting. Fix in progress. |
Followup: |
Fix #4728 Co-authored-by: nboisteault <[email protected]>
What is the question? (in English)
Hi,
After upgrading from 3.7.10 to 3.8.0, , I am surprised to notice that with hyperlinks added in several popup fields, the
target="_blank"
attribute is no longer interpreted in LWC.Linked pages now opens in the same tab as LWC even if the
target="_blank"
attribute is clearly specified in the tags (either in the popup tooltips or directly in the value of the field used to display hyperlinks). Anyway,target="_blank"
attribute is not present in tags when I analyse source code in the browser console...Exemple of a field content used to display hyperlinks in Popup :
After downgrading to 3.7.10,
target="_blank"
attribute is back and functional.Any other similar feddbacks about this ?
Thanks !
Versions, safeguards, check summary etc
Versions :
List of safeguards :
Check Lizmap plugin
Operating system
Debian, Ubuntu
Browsers
Firefox, Chrome
Browsers version
Chromium 121, Firefox 128
Relevant log output
No response
The text was updated successfully, but these errors were encountered: