#73 [PATCH] correctly identify REMOVE_AUTO_REDIRECT

open
None
6
2010-09-23
2009-03-23
No

Hi,

We discovered that this meta:
<meta http-equiv="refresh" content="1; a.html" />
Was seen as a REMOVE_AUTO_REFRESH whereas actually it's
a REMOVE_AUTO_REDIRECT. We did this patch to fix the issue.

Thanks to this change REMOVE_AUTO_REDIRECT are detected in
this case:

<meta http-equiv="refresh" content="1 a" />
<meta http-equiv="refresh" content="1a" />
<meta http-equiv="refresh" content="1; a.html" />
<meta http-equiv="refresh" content="a.html" />
<meta http-equiv="refresh" content="http://a/a.html" />

And

REMOVE_AUTO_REFRESH in this cases:

<meta http-equiv="refresh" content="1" />
<meta http-equiv="refresh" content=" 1; " />
<meta http-equiv="refresh" content=" 1 " />

Reference: http://www.w3.org/TR/WCAG10-HTML-TECHS/#meta-element

Best regards,

Gonéri Le Bouder and Philippe Prados

Discussion

  • Arnaud Desitter

    Arnaud Desitter - 2009-03-25

    A few comments:
    #1 I can build some test cases. Do not worry.
    #2 post a patch produced by "diff -u"
    #3 wrong lengths in strncmp calls
    #4 please comment the code that sets "HasRedirect"

    Thanks for your efforts

     
  • Arnaud Desitter

    Arnaud Desitter - 2009-03-25
    • priority: 5 --> 6
    • assigned_to: nobody --> arnaud02
    • status: open --> open-accepted
     
  • Gonéri Le Bouder

    Hi Arnaud,

    I attached the new patch.

    Best regards,

    Gonéri

     
  • Gonéri Le Bouder

    • status: open-accepted --> open
     
  • Gonéri Le Bouder

    Hi,

    The patch resolution is "Accepted" but the patch has not been applied. Can you please have a look.

    Best regards

     
  • OSC Member

    OSC Member - 2011-02-07

    Hi,

    The patch's still open.
    Do you plan to integrate it ?

    Regards

     

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks