896 2004-09-28 13:13:47 +0000 "summary mode" can cause browser timeout 2004-11-23 20:14:52 +0000 1 1 1 Unclassified LinkChecker checklink 4.0 Other other RESOLVED FIXED P2 normal 4.1 1 ot ot ville.skytta www-validator-cvs oldest_to_newest 2380 0 ot 2004-09-28 13:13:47 +0000 The "summary only" mode sends no output while processing all the links. Given how this phase can take up to minutes, some browsers consider it as a "server timeout". Issue already discussed in http://lists.w3.org/Archives/Public/public-qa-dev/2004Sep/0091.html but no obvious solution found yet. 2532 1 ville.skytta 2004-10-12 21:57:44 +0000 Candidate fix in CVS: http://dev.w3.org/cvsweb/perl/modules/W3C/LinkChecker/bin/checklink.diff?r1=4.7&r2=4.8&f=h As discussed in today's meeting, reassigning to Olivier for the "this may take some time" message in summary only mode (probably good to have for both cmdline and CGI). 2604 2 ot 2004-11-11 03:56:20 +0000 Will take care of the "this may take some time" message, accepting assignment 2605 3 ot 2004-11-11 06:49:50 +0000 "this may take some time" message added. A few tests revealed that although most browsers react well to the 'print spaces' hack, others don't. Notably, Mac OSX's safari doesn't even start rendering the page (and thus does not show the "this may take some time" message) before, apparently, having received "enough" content, and thus fails with a timeout error. Arguably, this is a browser bug, and there is little we can do about it beyond mentioning in the documentation that with some browsers, it is safer to not use the "summary only" option... Your thoughts? 2609 4 ville.skytta 2004-11-12 20:05:29 +0000 Ok, let's just document it now and get 4.1 out, and keep eyes open for better implementations/workarounds in the future. 2647 5 ville.skytta 2004-11-23 20:14:52 +0000 Comment 3 noted in the docs.