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
{{ message }}
This repository has been archived by the owner on Mar 28, 2024. It is now read-only.
See attached screenshot. At any point below the line goodstring="£" (that's a UK Pound currency symbol) the location picked up by 'follow cursor' appears to be off-by-one, likely through failing to account for a multi-byte character in some way.
To reproduce the bug enter the script as in the picture, open Keyword Help/LSL Reference and turn on "Follow Cursor".
Click on line 0 'integer' - the keyword help for integer shows
Click on line 1 'string' - the keyword help for string shows
Click on line 2 'integer' - the keyword help will change back to integer
Click on link 3 'string' - the keyword help for string shows
Click on line 4 'integer' - you get the page as shown in the picture.
All references below that point exhibit similar behaviour.
Other symbols produce it too, such as € (the Euro currency symbol).
Tip for testers/coders: switch to a UK Windows keyboard layout. The £ symbol is shift-3 and the € symbol is alt-gr-4
"Follow Cursor" LSL Reference gets confused by some (multibyte?) symbols in strings
Type
Bug
Priority
Unset
Status
Closed
Resolution
Triaged
Reporter
Chorazin Allen (chorazin.allen)
Created at
2020-07-27T13:03:22Z
Updated at
2021-04-29T15:29:40Z
{
'Build Id': 'unset',
'Business Unit': ['Platform'],
'ReOpened Count': 0.0,
'Severity': 'Unset',
'System': 'SL Viewer',
'Target Viewer Version': 'viewer-development',
'What just happened?': 'See attached screenshot. At any point below the line goodstring="£" (that\'s a UK Pound currency symbol) the location picked up by \'follow cursor\' appears to be off-by-one, likely through failing to account for a multi-byte character in some way.\r\n\r\nTo reproduce the bug enter the script as in the picture, open Keyword Help/LSL Reference and turn on "Follow Cursor".\r\n\r\nClick on line 0 \'integer\' - the keyword help for integer shows\r\nClick on line 1 \'string\' - the keyword help for string shows\r\nClick on line 2 \'integer\' - the keyword help will change back to integer\r\nClick on link 3 \'string\' - the keyword help for string shows\r\nClick on line 4 \'integer\' - you get the page as shown in the picture.\r\nAll references below that point exhibit similar behaviour.\r\n\r\nOther symbols produce it too, such as € (the Euro currency symbol).\r\n\r\nTip for testers/coders: switch to a UK Windows keyboard layout. The £ symbol is shift-3 and the € symbol is alt-gr-4',
'What were you doing when it happened?': 'Wondering why the help looked strange',
'What were you expecting to happen instead?': 'Correct help content to be shown',
}
The text was updated successfully, but these errors were encountered:
What just happened?
See attached screenshot. At any point below the line goodstring="£" (that's a UK Pound currency symbol) the location picked up by 'follow cursor' appears to be off-by-one, likely through failing to account for a multi-byte character in some way.
To reproduce the bug enter the script as in the picture, open Keyword Help/LSL Reference and turn on "Follow Cursor".
Click on line 0 'integer' - the keyword help for integer shows
Click on line 1 'string' - the keyword help for string shows
Click on line 2 'integer' - the keyword help will change back to integer
Click on link 3 'string' - the keyword help for string shows
Click on line 4 'integer' - you get the page as shown in the picture.
All references below that point exhibit similar behaviour.
Other symbols produce it too, such as € (the Euro currency symbol).
Tip for testers/coders: switch to a UK Windows keyboard layout. The £ symbol is shift-3 and the € symbol is alt-gr-4
What were you doing when it happened?
Wondering why the help looked strange
What were you expecting to happen instead?
Correct help content to be shown
Other information
Attachments
Original Jira Fields
The text was updated successfully, but these errors were encountered: