#8885: HTML markup appearing in title of doc page
--------------------------------------+-------------------------------------
          Reporter:  gkelly           |         Owner:  nobody
            Status:  closed           |     Milestone:        
         Component:  Django Web site  |       Version:  1.0   
        Resolution:  fixed            |      Keywords:        
             Stage:  Accepted         |     Has_patch:  1     
        Needs_docs:  0                |   Needs_tests:  0     
Needs_better_patch:  1                |  
--------------------------------------+-------------------------------------
Comment (by kmtracey):

 Replying to [comment:14 ubernostrum]:
 > (In [11598]) Fixed #8885 and its many duplicates (hopefully) by
 stripping HTML (which implies mark_safe) to titles of documentation pages.

 striptags has is_safe=True but that won't explicitly mark the output as
 safe, it will just preserve the safe status of input.  We don't mark the
 title as safe, so it is still being escaped, which means titles with smart
 quotes, such as:

 http://docs.djangoproject.com/en/dev/ref/contrib/sites/ [[BR]]
 http://docs.djangoproject.com/en/dev/ref/contrib/comments/ [[BR]]
 http://docs.djangoproject.com/en/dev/internals/release-process/ [[BR]]
 http://docs.djangoproject.com/en/dev/topics/cache/ [[BR]]

 are still looking a bit odd. Could we also just explicitly run `doc.title`
 through the safe filter?

-- 
Ticket URL: <http://code.djangoproject.com/ticket/8885#comment:15>
Django <http://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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to 
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to