This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 5591 - Handling of Meta Refresh
Summary: Handling of Meta Refresh
Status: RESOLVED FIXED
Alias: None
Product: mobileOK Basic checker
Classification: Unclassified
Component: Web interface (show other bugs)
Version: unspecified
Hardware: All All
: P2 enhancement
Target Milestone: ---
Assignee: Dominique Hazael-Massieux
QA Contact:
URL: The question is, should we stop on me...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-03-27 16:18 UTC by Dominique Hazael-Massieux
Modified: 2011-01-14 10:50 UTC (History)
1 user (show)

See Also:


Attachments

Description Dominique Hazael-Massieux 2008-03-27 16:18:29 UTC
The question is, should we stop on meta refresh (because we may be testing a page the user never sees, or should we test the page anyway, as if the timeout is long enough, they will in fact see it).

Where does warning the user that the results may not refer to the page they tohout they were testing fit in to all this?

Should we actually follow Meta redirects, contrary to our religion?

(moved from tracker)
Comment 1 Sean Owen 2008-03-27 16:25:48 UTC
I vote no as mobileOK Basic does not specify this.
Comment 2 fd 2011-01-14 10:50:40 UTC
Meta refresh are not followed.