You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have checked that the bug exists in the dev-development branch Yes.
I have checked that there are no already open issues or recently closed issues about this bug Yes.
Describe the bug
Variable flagSrc for a language rendered by the LanguageMenuViewHelper does not contain the src of the image (anymore).
Until version v6.0.5 (and still in December 2021 on the development branch working fine for v11), the variable flagSrc of every language returned the src of the flag image which could then be used to render the image. Since commit ca9bbe4, the variable containes the HTML code of the rendered image.
To Reproduce
Use LanguageMenuViewHelper with layout flag for v7.0.1 oder dev-development
Inspect the variable flagSrc of any language item
Expected behavior
I would expect to get the actual image path from this variable, as it was before, and I could not find any documentation underlining that this change was intended.
The text was updated successfully, but these errors were encountered:
I have checked that the bug exists in the
dev-development
branchYes.
I have checked that there are no already open issues or recently closed issues about this bug
Yes.
Describe the bug
Variable
flagSrc
for a language rendered by theLanguageMenuViewHelper
does not contain the src of the image (anymore).Until version
v6.0.5
(and still in December 2021 on the development branch working fine forv11
), the variableflagSrc
of every language returned the src of the flag image which could then be used to render the image. Since commit ca9bbe4, the variable containes the HTML code of the rendered image.To Reproduce
LanguageMenuViewHelper
with layout flag forv7.0.1
oderdev-development
flagSrc
of any language itemExpected behavior
I would expect to get the actual image path from this variable, as it was before, and I could not find any documentation underlining that this change was intended.
The text was updated successfully, but these errors were encountered: