#14825: LocaleMiddleware should store language preferences if possible
--------------------------------------+------------------------------------
     Reporter:  vzima                 |                    Owner:  vzima
         Type:  New feature           |                   Status:  closed
    Component:  Internationalization  |                  Version:  master
     Severity:  Normal                |               Resolution:  fixed
     Keywords:                        |             Triage Stage:  Accepted
    Has patch:  1                     |      Needs documentation:  0
  Needs tests:  0                     |  Patch needs improvement:  0
Easy pickings:  0                     |                    UI/UX:  0
--------------------------------------+------------------------------------

Comment (by dave@…):

 This change has made multi-language testing much more difficult for
 authenticated Django applications.

 Prior to this commit, my QA team could follow this simple process to
 switch languages during testing:

 1. Switch language in browser settings
 2. Refresh page
 3. Test

 Now, they must do this:

 1. Switch language in browser settings.
 2. Clear session cookie
 3. Re-authenticate
 4. Navigate to page under test
 5. Test

 This behavior seems ok for the average user (whose language doesn't change
 minute to minute), but for a tester, this really makes things slow. Even
 test automation suffers (e.g., Selenium).

 Could we at least put this behavior being a setting? Something like
 setting.STORE_LANGUAGE_IN_SESSION = True|False (default True)

-- 
Ticket URL: <https://code.djangoproject.com/ticket/14825#comment:15>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/063.47fd4d054dc5acbc1e3ec22a1d27317a%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to