-
Bug
-
Resolution: Fixed
-
Major
-
4.0RC1
-
None
-
None
Currently, if I pass a JS string equals to
"This is my \"ametys\" description"
the tooltip will display "This is my "
If I want to display the right tooltip text, I must pass the string in JS
"This is my "ametys" description"
which means that if it is an i18n string, it should be declared as
<message key="MY_KEY">This is my &quot;ametys &quot; description</message>
in the XML catalogue
Automatically replacing the double quotes characters should be more user-friendly for non-developpers who write some i18n keys in messages_xx.xml catalogues
- Conditionne
-
MYFAVORITES-12 Missing exemple in a tooltip of the title field in the repeater of myfavorites content
-
- Closed
-
[RUNTIME-2322] Enable to write double quotes characters in ametysDescription
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Link |
New:
This issue Conditionne |
Description |
Original:
Currently, if I pass a JS string equals to
{code:java}"This is my \"ametys\" description" {code} the tooltip will display "This is my " If I want to display the right tooltip text, I must pass the string in JS {code:java}"This is my "ametys" description" {code} which means that if it is an i18n string, it should be declared as {code:java}<message key="MY_KEY">This is my &quot;ametys &quot; description</message> {code} in the XML catalogue Automatically replacing the double quotes characters should be more user-friendly for non-developpers who write some i18n keys in messages_xx.xml catalogues |
New:
Currently, if I pass a JS string equals to
{code:javascript}"This is my \"ametys\" description" {code} the tooltip will display "This is my " If I want to display the right tooltip text, I must pass the string in JS {code:javascript}"This is my "ametys" description" {code} which means that if it is an i18n string, it should be declared as {code:xml}<message key="MY_KEY">This is my &quot;ametys &quot; description</message> {code} in the XML catalogue Automatically replacing the double quotes characters should be more user-friendly for non-developpers who write some i18n keys in messages_xx.xml catalogues |