secondlife / jira-archive

2 stars 0 forks source link

[BUG-41102] Feature Request: URI namespace for /displayname & /completename should perform as namesake implies regardless of "View Display Names" viewer setting. #12688

Open sl-service-account opened 7 years ago

sl-service-account commented 7 years ago

Information

URI namespace for /displayname & /completename will not resolve when "View Display Names" viewer setting is disabled, but /username will.

Example:

With "View Display Names" disabled, secondlife:///app/agent/b91d12f1-4e0f-4752-8199-73d71fdeeee5/displayname returns "Lucia Nightfire" secondlife:///app/agent/b91d12f1-4e0f-4752-8199-73d71fdeeee5/completename returns "Lucia Nightfire" secondlife:///app/agent/b91d12f1-4e0f-4752-8199-73d71fdeeee5/username returns "lucia.nightfire"

With "View Display Names" enabled: secondlife:///app/agent/b91d12f1-4e0f-4752-8199-73d71fdeeee5/displayname should return "Lucy daughter of the Devil" secondlife:///app/agent/b91d12f1-4e0f-4752-8199-73d71fdeeee5/completename should return "Lucy daughter of the Devil (lucia.nightfire)" secondlife:///app/agent/b91d12f1-4e0f-4752-8199-73d71fdeeee5/username returns "lucia.nightfire"

Scripted applications do not explicitly rely on this viewer setting. They depend on the namespaces resolving as the namesake implies.

This feature request is for one of the following changes:

Links

Related

Original Jira Fields | Field | Value | | ------------- | ------------- | | Issue | BUG-41102 | | Summary | Feature Request: URI namespace for /displayname & /completename should perform as namesake implies regardless of "View Display Names" viewer setting. | | Type | New Feature Request | | Priority | Unset | | Status | Accepted | | Resolution | Accepted | | Reporter | Lucia Nightfire (lucia.nightfire) | | Created at | 2016-12-24T02:46:54Z | | Updated at | 2017-02-07T01:41:06Z | ``` { 'Business Unit': ['Platform'], 'How would you like the feature to work?': 'URI namespace for /displayname & /completename will not resolve when "View Display Name" viewer setting is disabled, but /username will.\r\n\r\nExample:\r\n\r\nWith "View Display Name" disabled,\r\nsecondlife:///app/agent/b91d12f1-4e0f-4752-8199-73d71fdeeee5/displayname returns "Lucia Nightfire"\r\nsecondlife:///app/agent/b91d12f1-4e0f-4752-8199-73d71fdeeee5/completename returns "Lucia Nightfire"\r\nsecondlife:///app/agent/b91d12f1-4e0f-4752-8199-73d71fdeeee5/username returns "lucia.nightfire"\r\n\r\nWith "View Display Name" enabled:\r\nsecondlife:///app/agent/b91d12f1-4e0f-4752-8199-73d71fdeeee5/displayname should return "Lucy daughter of the Devil"\r\nsecondlife:///app/agent/b91d12f1-4e0f-4752-8199-73d71fdeeee5/completename should return "Lucy daughter of the Devil (lucia.nightfire)"\r\nsecondlife:///app/agent/b91d12f1-4e0f-4752-8199-73d71fdeeee5/username returns "lucia.nightfire"\r\n\r\nScripted applications do not explicitly rely on this viewer setting. They depend on the namespaces resolving as the namesake implies.\r\n\r\nThis feature request is for one of following changes:\r\n\r\n- A) Change behavior of /displayname & /completename to resolve as their namesake implies regardless of the "View Display Name" viewer setting.\r\n\r\n- B) A new URI path /show or /display that can be added to the tree to explicitly resolve /displayname or /completename regardless of the "View Display Name" viewer setting.\r\n\r\nWith one of these changes, scripted applications can perform as expected.\r\n\r\nThanks in advance for any consideration.', 'ReOpened Count': 0.0, 'Severity': 'Unset', 'Target Viewer Version': 'viewer-development', 'Why is this feature important to you? How would it benefit the community?': '?', } ```
sl-service-account commented 7 years ago

Lucia Nightfire commented at 2017-02-07T01:11:58Z, updated at 2017-02-07T01:15:43Z

In viewer Second Life 5.0.2.323359 (Second Life Release) it appears the View Display Name setting has been broken and no actual change to /displayname & /completename namespaces have been made.

Also in viewer Second Life 5.0.1.323027 (Second Life Release) it appears the Usernames setting is returning legacy name instead of user name in agent name tags.

sl-service-account commented 7 years ago

Lucia Nightfire commented at 2017-02-07T01:32:22Z

Ok, the uri's finally resolved themself after group chat occurred or when another agent using a display name chatted.

The problem now is that the Usernames setting is still referenced with /completename namespaces.

Will file a new jira.