Closed Bug 1654245 Opened 5 years ago Closed 5 years ago

Clarify server parameter is optional (e.g. when using SRV records)

Categories

(Chat Core :: XMPP, defect)

defect

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: mf, Unassigned)

References

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_6) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/13.1.2 Safari/605.1.15

Steps to reproduce:

I tried to connecting to an XMPP server that implements XEP-0368 ( https://compliance.conversations.im/test/xep0368/ ). It means while my username is user@example.com, the actual server address is chat.example.com. However, account adding UX doesn't indicate that at the last step "server" setting is optional and will override everything that is checked under XEP-0368. Thus if I simply type "example.com" there, as my username suggests, my connections will fail without explicit error.

Actual results:

Thunderbird XMPP connection times out on every attempt. No error is provided.

Expected results:

Thunderbird XMPP connection should follow SRV records and automatically adjust the server name if the value provided explicitly in "server" creates connection errors. OR the UI should provide some error message.

Summary: Implement XEP-0368: SRV records for XMPP over TLS → Tweak UX around XEP-0368: SRV records for XMPP over TLS
Component: Untriaged → Instant Messaging
Blocks: tb78found

I tried to clarify the title a bit, hopefully I got it right.

I suspect we can simply add an "(optional)" to the server setting to make it clearer that it doesn't need to be provided.

Component: Instant Messaging → XMPP
Product: Thunderbird → Chat Core
Summary: Tweak UX around XEP-0368: SRV records for XMPP over TLS → Clarify server parameter is optional (e.g. when using SRV records)

Well, the wizard has a big text on top "Feel free to skip this step if you want to" (== everything is optional). So I don't think I see what we should change here.

I think we can close this, per comment 2 there's not much more we could/should do.

Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.