This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Back to bug 5591
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| srowen | 2008-03-27 16:25:48 UTC | URL | 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 enoughthey 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? http://www.w3.org/2005/MWI/BPWG/Group/track/issues/214 | 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 enoughthey 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? http://www.w3.org/2005/MWI/BPWG/Group/track/issues/214 |
| Severity | normal | enhancement | ||
| OS | Linux | All | ||
| Hardware | PC | All | ||
| dom | 2008-06-25 14:30:28 UTC | Assignee | srowen | dom |
| Component | Java Library | Web interface | ||
| fd | 2011-01-14 10:50:40 UTC | Status | NEW | RESOLVED |
| CC | fd | |||
| Resolution | --- | FIXED |
Back to bug 5591