[Bug 32125] Should support auth using captcha

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=32125

--- Comment #43 from Dario Freddi <drf54321 at gmail.com> 2012-02-15 02:29:18 PST ---
(In reply to comment #42)
> (In reply to comment #41)
> > What if protocol specifies the label anyway even if the challenge is,
> > say, OCR?
> 
> (XMPP does.)
> 
> Then we give the Handler as much information as possible, and let it make its own decision depending on UI policy and the value of Language: it can either
> display what the server gave it, or its own translated string; or even something like displaying the server's string if its Language matches the current
> locale, or both strings if not.

I see your point

> 
> > wouldn't it
> > make sense to
> > ditch the label property in the structure, and provide the label in the
> > payload instead?
> 
> I did consider putting the "qa" question in as a "text/plain" payload, but there doesn't seem a whole lot of point in special-casing it, if labels exist at
> all.
> 
> One difference between "qa" and the others is that for any other captcha type, you're expected to display the Label (or your own localized version of it) *and*
> the payload, whereas for "qa" (afaics) you're expected to display the Label (question) only:
> 
>   /-[Captcha]---------------\           /-[Captcha]---------\
>   | Type the words you see: |           | What is 2+2?      |
>   | /------------------\    |      vs.  |                   |
>   | | spleen Belgium   |    |           | [_______________] |
>   | \------------------/    |           \-------------------/
>   | [_____________________] |
>   \-------------------------/

I don't see this as the main issue, as generally a handler receiving a payload with text/plain should figure out it's suppose to display that text only.
However, in the end I think the spec is ok this way due to what you said about XMPP before and the fact that we might be hiding information if we went down the
payload-and-no-label way.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA Contact for the bug.